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

Malformed Artifact Repository IAM binding URL #934

Open
jtmarmon opened this issue Nov 20, 2023 · 0 comments
Open

Malformed Artifact Repository IAM binding URL #934

jtmarmon opened this issue Nov 20, 2023 · 0 comments
Labels
kind/bug Some behavior is incorrect or out of spec service/iam

Comments

@jtmarmon
Copy link

jtmarmon commented Nov 20, 2023

What happened?

I tried creating a artifactregistry.RepositoryIamBinding and was getting a 403, despite being able to successfully create the same binding via the CLI. Adding trace logs shows that the request URL seems to be malformed (note the repository section):

    I1120 17:47:42.413470   42663 log.go:81] HTTP Response Begin GET [https://artifactregistry.googleapis.com/v1/projects/myproject/locations/us-east1/repositories/%7BrepositoriesId%7D:getIamPolicy] [Length: -1] ===================================================
    HTTP/2.0 403 Forbidden

Switching to the classic provider fixed my issue for now.

Example

    const repository = new artifactregistry.Repository("repository", {
      repositoryId: "repo",
      format: "DOCKER",
      location: "us-east1",
    });
    const binding = new artifactregistry.RepositoryIamBinding(
        `repo-binding`,
        {
          members: ['user:[email protected]'],
          role: "roles/artifactregistry.reader",
          name: "repo",
        }
      );

Output of pulumi about

CLI
Version      3.91.0
Go Version   go1.21.3
Go Compiler  gc

Plugins
NAME           VERSION
gcp            7.1.1
google-native  0.31.1
nodejs         unknown

Host
OS       darwin
Version  14.1
Arch     arm64

Additional context

No response

Contributing

Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

@jtmarmon jtmarmon added kind/bug Some behavior is incorrect or out of spec needs-triage Needs attention from the triage team labels Nov 20, 2023
@mikhailshilkov mikhailshilkov added service/iam and removed needs-triage Needs attention from the triage team labels Nov 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Some behavior is incorrect or out of spec service/iam
Projects
None yet
Development

No branches or pull requests

2 participants