gcloud: support GCE_ZONE_ID to bypass zone list #2073
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hello, Your PR comes from a GitHub Organization, it's a problem to edit your PR and for automation that modifies or updates PR. Can you re-create your PR from a personal fork? |
The GCloud IAM permission system permits a zone to grant access to an actor, without the project granting any access. This can be used with Service Accounts to let an SA edit DNS in one particular zone, and nothing more. Remove the need for the caller to have project-level role access granting the `dns.managedZones.list` permission, in exchange for the caller telling us the explicit zone ID to use, via the `GCE_ZONE_ID` environment variable.
Restructure to reduce complexity, rename variables for compatibility, and use `golangci-lint run --fix` before check-in.
Done, this has been re-forked and a new PR submitted, #2081. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The GCloud IAM permission system permits a zone to grant access to an actor, without the project granting any access. This can be used with Service Accounts to let an SA edit DNS in one particular zone, and nothing more.
Remove the need for the caller to have project-level role access granting the
dns.managedZones.listpermission, in exchange for the caller telling us the explicit zone ID to use, via theGCE_ZONE_IDenvironment variable.PR comment: sorry, I'm going to need help figuring out the test rig and how to set it up to fail the managedzones list call but succeed on zone edits, to add a test for this logic.