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

aws_autoscaling_group ignore_changes on min/max size not working as expected #1108

Closed
gservat opened this issue Jul 11, 2017 · 2 comments
Closed

Comments

@gservat
Copy link

gservat commented Jul 11, 2017

Terraform Version

v0.9.10

Affected Resource(s)

  • aws_autoscaling_group

Terraform Configuration Files

resource "aws_autoscaling_group" "groups" {
   count = "${length(var.availability_zones)}"

   min_size = 1
   max_size = 2

   ...
   lifecycle {
     ignore_changes = ["min_size", "max_size"]
   }
   ...
}

I made a change to the max size on the AWS console for one of the ASGs.

Expected Behavior

No changes to infrastructure since max_size is in the ignore_changes list.

Actual Behavior

Issuing a terraform plan shows changes to be made to the max_size.

~ module.asg.aws_auto_scaling_group.groups.0
    max_size: "5" => "4"

Steps to Reproduce

  1. Create asg.tf with an aws_autoscaling_group definition that has include_changes = ["min_size", "max_size"]
  2. Once the ASG is created, attempt to update the min or max via AWS console
  3. Run terraform plan - if successfully reproduced it should show changes to be made.

References

hashicorp/terraform#5627

@gservat
Copy link
Author

gservat commented Jul 12, 2017

Apologies. Embarrassing PEBKAC issue. ignore_changes works fine 😄

@gservat gservat closed this as completed Jul 12, 2017
@ghost
Copy link

ghost commented Apr 11, 2020

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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!

@ghost ghost locked and limited conversation to collaborators Apr 11, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant