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_availability_zones started proposing changes on each apply #14623

Closed
vladimirtiukhtin opened this issue Aug 13, 2020 · 2 comments
Closed
Labels
service/ec2 Issues and PRs that pertain to the ec2 service.

Comments

@vladimirtiukhtin
Copy link

Just would like to reopen #14405 as it seems got abandoned

Terraform CLI and Terraform AWS Provider Version

Terraform v0.13.0
+ provider registry.terraform.io/hashicorp/aws v3.1.0
+ provider registry.terraform.io/hashicorp/random v2.3.0

Affected Resource(s)

  • aws_availability_zones

Debug Output

Screen Shot 2020-08-13 at 14 04 56

Expected Behavior

No changes proposed

@ghost ghost added the service/ec2 Issues and PRs that pertain to the ec2 service. label Aug 13, 2020
@github-actions github-actions bot added the needs-triage Waiting for first response or review from a maintainer. label Aug 13, 2020
@bflad
Copy link
Contributor

bflad commented Aug 13, 2020

Hi @vladimirtiukhtin 👋 Sorry for the confusion here, while the group_names fix applied in Terraform AWS Provider version 3.1.0 was an actual issue, it was not the only issue occurring.

There was some unexpected changes with data source handling that occurred in the Terraform CLI version 0.13.0 release that are causing this additional data source output in addition to the unstable id attribute in the output. There are now larger tracking issues for both sides of this so to consolidate efforts and discussions, I'm going to close this in preference of them:

Please upvote and subscribe to those for further updates. 👍

@bflad bflad closed this as completed Aug 13, 2020
@ghost
Copy link

ghost commented Sep 12, 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 Sep 12, 2020
@breathingdust breathingdust removed the needs-triage Waiting for first response or review from a maintainer. label Sep 17, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
service/ec2 Issues and PRs that pertain to the ec2 service.
Projects
None yet
Development

No branches or pull requests

3 participants