resource/aws_appautoscaling_target: Support updating max_capacity, min_capacity, and role_arn attributes #2950
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.
This is a simplified remake of the #2542 PR after the IAM service role changes that needed to get in as part of #2889. The
basic
test already handles updating the max/min capacities and checking their values in state, hence why no test changes for them. Adding a check for IAM role updates I think is a can of worms given the weird IAM service role half state in AWS at this point.The RegisterScalableTarget API call supports updating attributes on existing targets.
Closes #240 and potentially #968