ci: add plan_only dry-run mode to reusable terraform deploy#73
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds an opt-in
plan_onlyinput to the reusable Terraform deploy workflow so callers can run a pull-request dry run without applying changes.Design
When
plan_onlyis true, Terraform initializes withterraform init -backend=false, so import adoption and planning run against isolated local state that is discarded with the runner workspace. The existing S3 backend initialization remains on the default deploy path.The dry-run path publishes
plan-output.txtto the job summary for review while keeping the existing plan artifact. The apply step and AWS OIDC configuration are gated to the default deploy path only.Safety
The default remains
plan_only: false. In that mode the S3 backend init and apply behavior are unchanged. Inplan_onlymode the canonical S3 state is not initialized andterraform applyis skipped.Verification
git diff --check.github/workflows/reusable-terraform-deploy.yamlwith PyYAMLterraform -chdir=terraform fmt -check -recursiveLocal Terraform init/validate/test could not run because the available local Terraform binaries are 1.15.2 and 1.14.3, while the module pins
required_version = "= 1.15.4".