-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
feat!: Add support for user_data_replace_on_change, and updated AWS provider to v4.7+ #272
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
feat!: Add support for user_data_replace_on_change, and updated AWS provider to v4.7+ #272
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please update versions.tf
to use AWS provider 4.7 as the minimum requirement in root module and in the examples. This PR will produce a major release.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you fix the failed checks (run pre-commit run -a
and commit the changes locally) and I will merge this?
I have fixed it for you. :)
This PR is included in version 4.0.0 🎉 |
Thank you! I appreciate all the help on this 🙏 |
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Description
Add support for user_data_replace_on_change attribute
Motivation and Context
Update to match aws provider feature
Breaking Changes
I don't believe so, it only adds a bool var with default set to aws provider default.
How Has This Been Tested?
examples/*
to demonstrate and validate my change(s)examples/*
projectspre-commit run -a
on my pull request