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

Error: Instance data.aws_region.current data could not be decoded from the state unsupported attribute "current #14763

Closed
coffeedome opened this issue Aug 20, 2020 · 6 comments
Labels
bug Addresses a defect in current functionality. upstream-terraform Addresses functionality related to the Terraform core binary.

Comments

@coffeedome
Copy link

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform CLI and Terraform AWS Provider Version

Terraform v0.12.24, hashicorp/aws v2.70.0

Affected Resource(s)

data "aws_region" "current" {}

Terraform Configuration Files

data "aws_region" "current" {}

Debug Output

Expected Behavior

Terraform plan runs without issue

Actual Behavior

ALL my team's pipelines have suddenly started failing when running terraform plan with the same error. This is across the board and no changes on our pipelines were made from the time things were working to the time this issue started.

Error: Invalid resource instance data in state

on main.tf line 19:
19: data "aws_region" "current" {}

Instance data.aws_region.current data could not be decoded from the state:
unsupported attribute "current".

Steps to Reproduce

  1. terraform plan with the versions specified above.

Important Factoids

References

image

  • #0000
@github-actions github-actions bot added the needs-triage Waiting for first response or review from a maintainer. label Aug 20, 2020
@DaemonDude23
Copy link

Running the command mentioned here resolved this same error for me: hashicorp/terraform#25819 (comment)

@marco-lancini
Copy link

I can reproduce @estebanes22 issue, and the fix proposed in hashicorp/terraform#25819 (comment) did not solve the issue for me, unfortunately

@nigelellis
Copy link

nigelellis commented Aug 25, 2020

I also hit this issue while attempting the upgrade to 0.13.0 and had to rollback to 0.12.29. This looks like a duplicate of hashicorp/terraform#25752 which is supposed to be fixed in the next release (0.13.1).

@marco-lancini
Copy link

Upgraded to 0.13.1 and can confirm the error seems resolved

@bflad bflad added bug Addresses a defect in current functionality. upstream-terraform Addresses functionality related to the Terraform core binary. and removed needs-triage Waiting for first response or review from a maintainer. labels Aug 27, 2020
@bflad
Copy link
Contributor

bflad commented Aug 27, 2020

Thanks for the confirmation, @marco-lancini. This should be resolved with Terraform CLI 0.13.1. 👍

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

ghost commented Sep 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 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 27, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Addresses a defect in current functionality. upstream-terraform Addresses functionality related to the Terraform core binary.
Projects
None yet
Development

No branches or pull requests

5 participants