Everything as Code with OpenTofu and Custom Providers

We will go into the best practices for adopting Everything as Code, using authorization as a case study. We’ll also discuss the current state and roadmap of OpenTofu, including a migration guide from Terraform to OpenTofu. Learn about the reasons for developing custom providers and the lessons learned from building Permit custom providers.

We’ll discuss:

- The shift from Infrastructure as Code to Everything as Code
- Best practices for adopting Everything as Code
- Authorization as a case study in transitioning to Everything as Code
- The current state and roadmap of OpenTofu
- A migration guide from Terraform to OpenTofu
- Reasons for developing custom providers
- Testing practices for Infrastructure as Code (IaC)
- DevOps and non-DevOps perspectives on IaC
- GitOps and how to adopt it without dedicated tools
- Practices for successful IaC automation processes
- Policy as code vs configuration as code
- Configuration as code for Policy as Code
- Open core and its fate
- Q&A