google_project_iam_member multiple roles
Reimagine your operations and unlock new opportunities. User creation is not actually relevant to the case. I am definitely still encountering this issue with 2.20.1, is it possible that version does not yet include the fix? Sign in Please fix. By clicking Post Your Answer, you agree to our terms of service, privacy policy and cookie policy. I believe that removing these faulty members will cause terraform to succeed. reference to see if the permission is granted by the role. Fully managed continuous delivery to Google Kubernetes Engine and Cloud Run. Tool to move workloads and existing applications to GKE. ID: A unique identifier for the role. Permissions are granted to your project members via roles. Streaming analytics for stream and batch processing. Not the answer you're looking for? When you're creating a custom role, choose an ID, title, and description that Solution to modernize your governance, risk, and compliance function with automation. google_project_iam_member is used to define a single user:role pairing. descriptions to see which @slevenick The project does have one user with capital letters in the email, though none of bindings defined via terraform do anything with that user. Two other differences seem to be in the headers: I am also seeing this issue when applying iam_member with provider.google: version = "~> 3.4", Error: Batch "iam-project-