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

Ignore Changes to ASG desired/min/max size #4696

Closed
ElliotG opened this issue Jan 16, 2016 · 2 comments
Closed

Ignore Changes to ASG desired/min/max size #4696

ElliotG opened this issue Jan 16, 2016 · 2 comments

Comments

@ElliotG
Copy link
Contributor

ElliotG commented Jan 16, 2016

This is either a bug, a misunderstanding of the feature, or a feature request. I'm attempting to set up an ASG via terraform. The capacity is managed by an external source, which then blocks all Terraform applys until someone updates the terraform plan manually:

Repro:

  1. Create an ASG of size 1 via Terraform
  2. Modify the ASG in the console to size 2
  3. Modify the launch configuration of the ASG
  4. Run a terraform plan (note that this looks correct)
  5. Run a terraform apply

Barf:

* aws_autoscaling_group.sweet-servers: diffs didn't match during apply. This is a bug with Terraform and should be reported.

It seems like terraform plan correctly respects the "ignore changes", but Terraform apply does not.

Any advice? Is this known?

Terraform snippet because why not:

resource "aws_autoscaling_group" "sweet-servers" {
    desired_capacity          = 1
    max_size                  = 1
    min_size                  = 1
    }

    lifecycle {
        ignore_changes = [ "desired_capacity", "max_size", "min_size" ]
    }
}
@phinze
Copy link
Contributor

phinze commented Mar 14, 2016

Hi @ElliotG - this is definitely a bug in Terraform. I'm rolling up ignore_changes issues in #5627 and tackling fixes today.

@phinze phinze closed this as completed Mar 14, 2016
@ghost
Copy link

ghost commented Apr 27, 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 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.

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

No branches or pull requests

3 participants