Skip to content
This repository has been archived by the owner on Jul 11, 2023. It is now read-only.

availability zones of asg module should be removed. #242

Open
Magicloud opened this issue Aug 23, 2019 · 5 comments
Open

availability zones of asg module should be removed. #242

Magicloud opened this issue Aug 23, 2019 · 5 comments
Assignees

Comments

@Magicloud
Copy link
Contributor

After upgrading to terraform 0.12, it happened to me that code using asg module cannot be applied sometimes, with "inconsistent plan" error. After trying the fix of following issue, it seemed working fine.

hashicorp/terraform-provider-aws#9622

@Magicloud
Copy link
Contributor Author

@ketzacoatl Please review the reference issue and the purposal before I submit PR.

@ketzacoatl
Copy link
Contributor

Yep, that LGTM. Maybe you can have @JoseD92 make the updates?

@JoseD92
Copy link
Contributor

JoseD92 commented Sep 4, 2019

@Magicloud I was able to reproduce the "inconsistent plan" error, and deleting the availability zones from the asg module does solve the issue, but as stated in the docs for aws_autoscaling_group, availability zones is Required only for EC2-Classic, the asg module would become useless if working with EC2-Classic, I am not sure if that is a use case for terraform-aws-foundation or not, but in the case it is, I think a better solution would be adding warnings in the readme of asg module and add assertions (preferably if the can run on both planning and applying) so that terraform exits with an error and an informative message if availability_zones and vpc_zone_identifier are used at the same time

@ketzacoatl
Copy link
Contributor

Great review and comment @JoseD92! I think it's ok for us to skip out on support for EC2 classic at this point. We should only see non-classic EC2 from now on.

@JoseD92
Copy link
Contributor

JoseD92 commented Sep 6, 2019

I add a MR with the fix

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

3 participants