feat(gcp): support organization-wide deployment#54
Merged
Conversation
Add a read-only hierarchy-browse binding (roles/browser) at org and folder scope so Nullify can enumerate projects under the chosen scope for org-wide and folder-wide installs. Not granted for scope=projects where the customer enumerates projects explicitly. Uses for_each over local.discovery_roles so stable binding keys and future additional discovery roles are a one-line add. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
pratulyakashyap-nullify
approved these changes
Jun 24, 2026
tim-thacker-nullify
approved these changes
Jun 24, 2026
This file contains hidden or 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
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.
Summary
Adds support for organization-wide deployment of the Nullify GCP integration, alongside the existing per-project setup. With
scope = "organization"(or"folder"), Nullify can enumerate and cover every project under the organization/folder — including projects created later — from a single Terraform apply, with no per-project onboarding.What changed
roles/browserbinding (read-only) granted to the Nullify service account, only forscope = "organization"andscope = "folder". This lets Nullify enumerate the projects under the chosen scope so org-wide installs auto-cover current and future projects. It grants no resource-data access (hierarchy browse only) and is not granted forscope = "projects".examples/organizationexample is annotated accordingly.Backward compatibility
Existing per-project installs are unaffected — no new bindings or behavior for
scope = "projects", and no new variables.Testing
terraform fmt -check -recursiveandterraform validatepass (Google provider v6).🤖 Generated with Claude Code
Need help on this PR? Tag
/codesmithwith what you need. Autofix is disabled.