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

google_project_iam_member does not store project in state #4455

Closed
scjody opened this issue Sep 13, 2019 · 3 comments · Fixed by GoogleCloudPlatform/magic-modules#2332
Closed
Assignees
Labels

Comments

@scjody
Copy link

scjody commented Sep 13, 2019

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 "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.

Terraform Version

Terraform v0.12.8
+ provider.google v2.14.0

Affected Resource(s)

  • google_project_iam_member

First set of resources:

provider "google" {
  credentials = "${file("../reef_303.json")}"
  project     = "plotly-testing"
}

resource "google_service_account" "storage_admin" {
  account_id   = "jody-temp-5"
  display_name = "jody-temp-5"
}

resource "google_project_iam_member" "storage-admin" {
  role   = "roles/storage.admin"
  member = "serviceAccount:${google_service_account.storage_admin.email}"
}

Second set of resources (the project has been moved from the provider to the actual resources).

provider "google" {
  credentials = "${file("../reef_303.json")}"
}

resource "google_service_account" "storage_admin" {
  project      = "plotly-testing"
  account_id   = "jody-temp-5"
  display_name = "jody-temp-5"
}

resource "google_project_iam_member" "storage-admin" {
  project = "plotly-testing"
  role    = "roles/storage.admin"
  member  = "serviceAccount:${google_service_account.storage_admin.email}"
}

Debug Output

Panic Output

N/A

Expected Behavior

  • 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).

Actual Behavior

Steps to Reproduce

  1. terraform apply with the first set of resources shown above.
  2. 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

@ghost ghost added the bug label Sep 13, 2019
@slevenick
Copy link
Collaborator

Thanks for the report! I've got a fix for this on the way

@slevenick
Copy link
Collaborator

This fix will be in the next release of the provider.

@ghost
Copy link

ghost commented Oct 19, 2019

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 ghost locked and limited conversation to collaborators Oct 19, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants