Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

adapt name of plan analyze file in terraform recipe #79

Merged
merged 1 commit into from
Oct 9, 2023
Merged

adapt name of plan analyze file in terraform recipe #79

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/features/09-terraform.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -72,7 +72,7 @@ Terraform recipe automatically persists the plans in the .plans directory, in th
sources are located. Additionally, to the plan file in terraform format, these files will also be created:

* additional terraform plan formats (check the dedicated section below)
* a file indicating if the plan contains no changes (*.deploy.plan-has-no-changes). In case of changes, there will be no file created.
* a file indicating if the plan contains no changes (*.deploy.tfplan.plan-has-no-changes). In case of changes, there will be no file created.
Note: such file is only be created for the deploy flow(s), destroy will never generate such file, even on actually no changes for destroy.

These can be used in CI/CD for use cases like automatic approval on no terraform changes. If you don't want to rely on the existence of such *plan-has-no-changes* file,
Expand Down