-
-
Notifications
You must be signed in to change notification settings - Fork 556
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
fix: Allow multiple step adjustments for step scaling and v5.0 provider upgrade #240
fix: Allow multiple step adjustments for step scaling and v5.0 provider upgrade #240
Conversation
FYI - if we take a breaking change, we should make all breaking changes at once to reduce the amount of disruption #204 |
This PR has been automatically marked as stale because it has been open 30 days |
Unstale |
This PR has been automatically marked as stale because it has been open 30 days |
unstale |
resolved in #204 |
This issue has been resolved in version 7.0.0 🎉 |
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
Step scaling allows for multiple step adjustments to be configured.
Also bumped module to terraform v1.0 and aws provider v5.0.
Motivation and Context
Resolves: #236
Breaking Changes
Yes, anyone previously specifying
step_adjustments
will need to changestep_adjustment
config from a map to a list of maps as shown in the updated example.Also aws provider v5.0 upgrade.
How Has This Been Tested?
examples/*
to demonstrate and validate my change(s)examples/*
projectspre-commit run -a
on my pull request