Separate resource for aws_autoscaling_warm_pool from aws_autoscaling_group

[nitrocode]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

It would be nice if I can add a warm pool to an existing asg without having to update the existing asg resource. For instance, for aws_autoscaling_group I can add a lifecycle hook in-line using the input initial_lifecycle_hook or I can add the hook using the separate resource aws_autoscaling_lifecycle_hook.

I'd like to do the same with an aws_autoscaling_group and aws_autoscaling_warm_pool.

It's also a separate action in both cloudformation AWS::AutoScaling::WarmPool and in the aws autoscaling put-warm-pool so a separate resource in addition to the in-line method would be consistent.

New or Affected Resource(s)

• aws_autoscaling_warm_pool

Potential Terraform Configuration

resource "aws_autoscaling_warm_pool" "example" {
  autoscaling_group_name = aws_autoscaling_group.example.id
  pool_state             = "Stopped"
  min_size               = 4
}

References

• Original issue EC2 Auto Scaling Warm Pools #18705

cc: @ewbankkit, @akshayjain1996

[github-actions]

Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label.

If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you!

[github-actions]

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.