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.

Sign up for GitHub

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

Jump to bottom

Switching project ids in gcp stack file causes a deployment error #682

Open
raksiv opened this issue Jun 28, 2023 · 0 comments
Open

Switching project ids in gcp stack file causes a deployment error #682

raksiv opened this issue Jun 28, 2023 · 0 comments
Labels
bug Something isn't working

Comments

@raksiv
Copy link
Member

raksiv commented Jun 28, 2023

Bug Report

Only affects gcp deployments -

Changing the project id after an initial deployment causes an IAM Member role to reference a nonexisting resource when deploying an updated version of the project.

gcp:projects:IAMMember (pdfs-submissions):
error: 1 error occurred:
* Request Create IAM Members projects/vanilla-390621/roles/AK8vkiy6 serviceAccount:[email protected] for project “chocolate-49533 returned error: Batch request and retried single request "Create IAM Members projects/vanilla-390621/roles/AK8vkiy6 serviceAccount:[email protected] for project "chocolate-49533\” both failed. Final error: Error applying IAM policy for project "chocolate-49533": Error setting IAM policy for project "chocolate-49533": googleapi: Error 400: Role (projects/vanilla-390621/roles/AK8vkiy6) does not exist in the resource's hierarchy., badRequest
@raksiv raksiv added the bug Something isn't working label Jun 28, 2023
@jyecusch jyecusch transferred this issue from nitrictech/cli Sep 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@raksiv