We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
v0.9.10
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.
No changes to infrastructure since max_size is in the ignore_changes list.
max_size
ignore_changes
Issuing a terraform plan shows changes to be made to the max_size.
terraform plan
~ module.asg.aws_auto_scaling_group.groups.0 max_size: "5" => "4"
asg.tf
aws_autoscaling_group
include_changes = ["min_size", "max_size"]
hashicorp/terraform#5627
The text was updated successfully, but these errors were encountered:
Apologies. Embarrassing PEBKAC issue. ignore_changes works fine 😄
Sorry, something went wrong.
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!
No branches or pull requests
Terraform Version
v0.9.10
Affected Resource(s)
Terraform Configuration Files
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 theignore_changes
list.Actual Behavior
Issuing a
terraform plan
shows changes to be made to themax_size
.Steps to Reproduce
asg.tf
with anaws_autoscaling_group
definition that hasinclude_changes = ["min_size", "max_size"]
terraform plan
- if successfully reproduced it should show changes to be made.References
hashicorp/terraform#5627
The text was updated successfully, but these errors were encountered: