-
-
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: Added all instance refresh options, including scale in protection and standby instances #243
Conversation
… standby instances
We are also hitting this error now. I assume the |
Thanks for the PR - We hit the same issue:
One thing I'd like to bring to notice is the documentation for scale_in_protected_instances and standby_instances says Default values as |
Please open an issue on the AWS provider - this sounds like a bug for the provider |
I've opened hashicorp/terraform-provider-aws#33377 . You can avoid this bug by downgrading your AWS provider to 5.15.0. |
There is already a PR for the bug in the AWS provider. Consider upvoting it. hashicorp/terraform-provider-aws#33382 |
This is done. Thanks for your input. |
this should be resolved now with https://github.com/hashicorp/terraform-provider-aws/releases/tag/v5.16.2 |
Well no because not all options are available in the instance refresh block. This PR was to make them available regardless of the bug. |
that will require v5.x of the AWS provider and therefore a breaking change - this will be handled in #240 |
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
Not all preferences were available in the
instance_refresh
map. I've added the rest of them in.Motivation and Context
I was getting the below error when using the module:
Breaking Changes
Since all parameters are optional. There are no breaking changes
How Has This Been Tested?
examples/*
to demonstrate and validate my change(s)examples/*
projectspre-commit run -a
on my pull request