You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
a new capability that facilitates graceful shutdown of workloads deployed on Amazon Elastic Compute Cloud (Amazon EC2) instances by safely stopping and rescheduling workloads to other, non-terminating instances.
Amend the implementation of how variable "autoscaling_capacity_providers" gets passed down to this block to propagate the managed_draining setting in the same way as is done for managed_termination_protection. This will need to be gated so that it is only set for aws provider 5.34.0 and above.
Describe alternatives you've considered.
Additional context
The text was updated successfully, but these errors were encountered:
I'm going to lock this issue 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 similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Is your request related to a new offering from AWS?
Amazon recently announced managed instance draining
Is this functionality available in the AWS provider for Terraform?
Support for this was added to the terraform aws provider in release v5.34.0 and its use is documented here.
Is your request related to a problem? Please describe.
This feature is available by setting the managed_draining property on aws_ecs_capacity_provider but is not exposed in auto_scaling_group_provider
Describe the solution you'd like.
Amend the implementation of how variable "autoscaling_capacity_providers" gets passed down to this block to propagate the managed_draining setting in the same way as is done for
managed_termination_protection
. This will need to be gated so that it is only set for aws provider 5.34.0 and above.Describe alternatives you've considered.
Additional context
The text was updated successfully, but these errors were encountered: