Collin Newberry

This session will outline how to use IaC to provide release versioned infrastructure playbooks in a no-code framework. The goal of this is to reduce the cost of cloud infrastructure by maintaining multiple offline copies of the same infrastructure in codified playbooks with zero drift between online and offline environments.

We will outline an IaC architectural plan and style guide which will enable the adoption of this strategy and demonstrate the ability to build and deploy numerous environments from offline configuration with zero drift.

This framework provides many advantages over traditional IaC including:
- Cost reduction in cloud environments
- Ability to swing between environments seamlessly with minimal downtime
- Seamless DR testing and recovery operations with minimal passive costs
- Ability to automate BC tasks for cross regional cloud workloads
- Scalability of environments where traditional scaling options do not exist

The next evolution of DevOps is the adoption of no-code infrastructure for infrastructure as code. The decentralization of the codified infrastructure into remotely managed and versioned modules provides numerous benefits to the management and maintenance of the IaC playbooks and deployed infrastructure.

The use of no-code modules for IaC ensures complete compatibility of infrastructure across projects, allows versioning to manage dependencies within modules, prevents unwanted drift of the playbooks from the standard template, enables shift left and if written well can integrate seamlessly with large language models to allow code generation using AI tools.

In this session we will discuss an architecture for managing no-code terraform and how we can use style guides and release versioning to enforce dependencies and prevent code drift from standards. We will also give a brief demonstration of the no-code terraform modules being managed using AI with Github Copilot.