Skip to content
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

feat: Add instance_maintenance_policy to autoscaling group #251

Conversation

magreenbaum
Copy link
Member

Description

Add instance_maintenance_policy to aws_autoscaling_group.
https://docs.aws.amazon.com/autoscaling/ec2/userguide/ec2-auto-scaling-instance-maintenance-policy.html

Motivation and Context

hashicorp/terraform-provider-aws#34430

Breaking Changes

No.

How Has This Been Tested?

  • I have updated at least one of the examples/* to demonstrate and validate my change(s)
  • I have tested and validated these changes using one or more of the provided examples/* projects
  • I have executed pre-commit run -a on my pull request

@fertrevino
Copy link

thumbs up, this would be very useful

@antonbabenko antonbabenko merged commit d9bf968 into terraform-aws-modules:master Nov 22, 2023
7 checks passed
antonbabenko pushed a commit that referenced this pull request Nov 22, 2023
## [7.3.0](v7.2.0...v7.3.0) (2023-11-22)

### Features

* Add `instance_maintenance_policy` to autoscaling group ([#251](#251)) ([d9bf968](d9bf968))
@antonbabenko
Copy link
Member

This PR is included in version 7.3.0 🎉

Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 23, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants