Add trigger for terraform state for plan jobs #888
Merged
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.
Changes proposed in this pull request:
data
inputs for terraform in this repo. The proposed change here simply looks for updates to the statefile and fires the corresponding environment's "plan" step. It will still need the operator to review the changes and run the "apply" step so the application security groups are updated with the new ip ranges.Security considerations
No real changes to security, simply quickens the response between when AWS changes IP CIDR ranges and when we reflect these changes within CF ASGs.