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

Terraform 0.13.0: plan shows ID changes in data sources #25912

Closed
sblask opened this issue Aug 19, 2020 · 2 comments
Closed

Terraform 0.13.0: plan shows ID changes in data sources #25912

sblask opened this issue Aug 19, 2020 · 2 comments
Labels
bug duplicate issue closed because another issue already tracks this problem new new issue not yet triaged

Comments

@sblask
Copy link

sblask commented Aug 19, 2020

Terraform Version

$ terraform version
Terraform v0.13.0
+ provider registry.terraform.io/hashicorp/archive v1.3.0
+ provider registry.terraform.io/hashicorp/aws v2.70.0
+ provider registry.terraform.io/hashicorp/external v1.2.0
+ provider registry.terraform.io/hashicorp/random v2.3.0
+ provider registry.terraform.io/hashicorp/template v2.1.2
+ provider registry.terraform.io/hashicorp/vault v2.12.2

Expected Behavior

terraform plan -out plan should show no changes.

Actual Behavior

Since upgrading to Terraform 0.13.0 I get something like this:

 <= data "aws_availability_zones" "default"  {
        group_names = [
            "ap-southeast-2",
        ]
      ~ id          = "2020-08-19 03:57:14.226776 +0000 UTC" -> "2020-08-19 03:57:30.667586 +0000 UTC"
        names       = [
            "ap-southeast-2a",
            "ap-southeast-2b",
            "ap-southeast-2c",
        ]
        zone_ids    = [
            "apse2-az1",
            "apse2-az3",
            "apse2-az2",
        ]
    }

terraform apply plan does not fix the problem, in fact, it doesn't do anything.

Steps to Reproduce

  1. terraform init
  2. terraform plan -out plan
@sblask sblask added bug new new issue not yet triaged labels Aug 19, 2020
@mildwonkey
Copy link
Contributor

hi @sblask , I'm sorry you're experiencing this issue. It is a duplicate of #25812, and the problem should be be fixed in the next terraform release. I am going to close this as a duplicate. Thanks, and sorry again!

@mildwonkey mildwonkey added the duplicate issue closed because another issue already tracks this problem label Aug 19, 2020
@ghost
Copy link

ghost commented Oct 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 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 as resolved and limited conversation to collaborators Oct 11, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug duplicate issue closed because another issue already tracks this problem new new issue not yet triaged
Projects
None yet
Development

No branches or pull requests

2 participants