-
Notifications
You must be signed in to change notification settings - Fork 79
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.
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
chore: update external
provider to 2.3.3
#477
Conversation
📃📃 Plan summary 📃📃No changes detected (apply not needed): Changes detected (apply needed): 📃📃 Plan output 📃📃👉 terragrunt/accounts/legacy/crates-io-prod/crates-io:
👉 terragrunt/accounts/legacy/crates-io-staging/crates-io:
👉 terragrunt/accounts/legacy/releases-dev/release-distribution:
👉 terragrunt/accounts/legacy/releases-prod/release-distribution:
|
b0df45a
to
cb0cd6d
Compare
The only suspicious thing in the plan is EDIT: the snippet comes from #416 |
c5e1de8
to
850723e
Compare
After merging #416 the snippet doesn't appear anymore. I'll apply and merge this 👍 |
I didn't update
terragrunt/modules/sync-team
because I can't select an aws version. I will investigate that another time.Note
Note that the plan in the next comment was automatically generated by running
infratk plan-pr https://github.com/rust-lang/simpleinfra/pull/477 --clipboard
🎉For now, it just runs
terraform/terragrunt plan
on every directory where the lockfile changes.I plan to give a demo about the infratk tool soon