Infrastructure-as-Code pull request
Last updated 2026-06-04
An infrastructure-as-code (IaC) pull request applies a change to cloud infrastructure as reviewable, version-controlled code rather than a manual console edit. The change is expressed in a tool such as Terraform, Pulumi, CloudFormation, or a Kubernetes manifest, then proposed as a pull request, reviewed by the team, and merged through the normal GitOps workflow. Because the proposal lives in Git, automated checks can run against it first: a plan or dry run shows exactly which resources will be created, modified, or destroyed before anything touches the live environment. For example, a rightsizing change might appear as a one-line edit to an instance type that reviewers approve like any other diff. This keeps infrastructure auditable, reversible, and free of configuration drift, and it lets cost optimizations be reviewed like any other code change. LevelFour drafts each optimization as an IaC pull request, complete with the estimated savings and a cost diff, so teams approve and merge with full context.
Frequently asked questions
- How is an infrastructure-as-code pull request different from changing the cloud console directly?
- A console edit applies immediately with no review trail, while an IaC pull request expresses the change as version-controlled code that teammates review and merge through Git. This keeps the live environment matched to code, preserves an audit history, makes changes reversible, and prevents configuration drift.
- Why deliver cost optimizations as pull requests instead of applying them automatically?
- Delivering a cost change as a pull request keeps a human in the loop and Git as the single source of truth. Reviewers see the exact resource diff and estimated impact before merging, the change is auditable and reversible, and the live environment never drifts from its declared infrastructure-as-code definition.
LevelFour automates this across AWS, GCP, Azure, and Kubernetes with automated infrastructure-as-code pull requests.