-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Correctly handle domain-scoped projects with GCR #2169
Correctly handle domain-scoped projects with GCR #2169
Conversation
Hi! I'm the modular magician, I work on Magic Modules. Pull request statusesNo diff detected in terraform-google-conversion. New Pull RequestsI built this PR into one or more new PRs on other repositories, and when those are closed, this PR will also be merged and closed. |
Ping @emilymye (this is just an upstreaming so it's already been reviewed) |
Hi! I'm the modular magician, I work on Magic Modules. Pull request statusesterraform-provider-google-beta already has an open PR. New Pull RequestsI didn't open any new pull requests because of this PR. |
Hi! I'm the modular magician, I work on Magic Modules. Pull request statusesterraform-provider-google-beta already has an open PR. New Pull RequestsI built this PR into one or more new PRs on other repositories, and when those are closed, this PR will also be merged and closed. |
…. This is necessary to work correctly with domain-scoped projects in GCR: https://cloud.google.com/container-registry/docs/overview#domain-scoped_projects
Tracked submodules are build/terraform-beta build/terraform-mapper build/terraform build/ansible build/inspec.
09f492b
to
ff13ce5
Compare
Upstreams hashicorp/terraform-provider-google#4129 (review)
Release Note for Downstream PRs (will be copied)