-
Notifications
You must be signed in to change notification settings - Fork 156
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
Does not work with Terraform 0.13 on TFC #209
Comments
Hi @ktham! I tried reproducing the issue you reported but I was not able to. I created a new workspace and linked it to a test github repo that contained just the following code: terraform {
required_version = "0.13.0"
required_providers {
tfe = {
source = "hashicorp/tfe"
version = "0.21.0"
}
}
}
provider "tfe" {}
resource "tfe_organization" "test" {
name = "a-random-org-name"
email = "admin@company.com"
}
Are you still experiencing the same issue? |
Hi @koikonom ! Thanks for follow up. I experience this when trying to upgrade from 0.12.29 to 0.13.0. So first try doing the former, create a few resources, then do the upgrade and you'll run into this issue |
Hi @ktham, I tried that as well (set version to 0.12.29, plan, apply, set version to 0.13, plan, apply) and I'm still not able to hit the same error. Can you please set an environment variable TF_LOG with the value of 1, reproduce the issue and send us the log in a gist? (Be careful not to include any tokens or other sensitive information) |
I'm also having same issue. I will also try to get a log. |
Plan Truncated large sections of this due to sheer size...Tried to leave the interesting bits... Apply |
Excellent, thank you very much for the logs. I will look into it and get back to you! |
BTW, I can confirm a new workspace using the TFE provider with no existing state works fine within my TF Cloud organization. |
This is also reported in hashicorp/terraform#26075 . As a (one-off) workaround please use the In this case the command should be: |
That worked to clear the issue for me. |
That worked for me also. Thanks guys! I'll close this issue |
Error msg
Provider version
The text was updated successfully, but these errors were encountered: