ci(terraform): amend inputs for drift detection #36
Conversation
This file contains 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
|
This is great. Thanks again for your input. I have a few other things (multi env) to work on for the drift detection workflow; i'll incorporation these changes when I do that. |
|
Resolved in #38 |
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.
Hashicorp documentation recommends running a
-refresh-onlyplan "to determine the drift between your current state file and actual configuration."While there, also bumped up the version tag and disabled PR labelling since a cron-scheduled workflow isn't associated with a PR (to minimize hassle, the PR-labelling step errors out quietly even if
label-pr: falseis not supplied).