You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 "me too" comments, 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
If an issue is assigned to the "modular-magician" user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If an issue is assigned to a user, that user is claiming responsibility for the issue. If an issue is assigned to "hashibot", a community member has claimed the issue already.
When terraform apply is run with the first set of resources, terraform.tfstate should contain a project for the google_project_iam_member resource. (All other google_* resources that need a project do this as far as I can see.)
terraform apply with the second set of resources should succeed (with no changes to apply).
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. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks!
ghost
locked and limited conversation to collaborators
Oct 19, 2019
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Community Note
Terraform Version
Affected Resource(s)
First set of resources:
Second set of resources (the
project
has been moved from theprovider
to the actual resources).Debug Output
terraform apply
is run with the first set of resources: https://gist.github.com/scjody/300e3becb3fe163ded53ea80c82307b2terraform apply
is run with the second set of resources: https://gist.github.com/scjody/2547f83386d6ca7ac96dc5a6e60bb259Panic Output
N/A
Expected Behavior
terraform apply
is run with the first set of resources,terraform.tfstate
should contain a project for thegoogle_project_iam_member
resource. (All othergoogle_*
resources that need a project do this as far as I can see.)terraform apply
with the second set of resources should succeed (with no changes to apply).Actual Behavior
terraform apply
is run with the first set of resources,terraform.tfstate
contains"project": null
. (Complete state: https://gist.github.com/scjody/614fea9445637ec601e60f7cbea4dce5)terraform apply
with the second set of resources fails with:Error: project: required field is not set
Steps to Reproduce
terraform apply
with the first set of resources shown above.terraform apply
with the second set of resources shown above.Workaround
To work around this issue, the state can be edited to change
"project": null
to"project": "plotly-testing"
.Important Factoids
N/A
References
The text was updated successfully, but these errors were encountered: