Skip to content

Add location-viewer role and include in networking-viewer#162

Open
scotwells wants to merge 2 commits into
mainfrom
feat/location-viewer-role
Open

Add location-viewer role and include in networking-viewer#162
scotwells wants to merge 2 commits into
mainfrom
feat/location-viewer-role

Conversation

@scotwells
Copy link
Copy Markdown
Contributor

Summary

  • Adds networking.datumapis.com-location-viewer role with list/get/watch on locations
  • Adds networking.datumapis.com-location-viewer to the inheritedRoles of networking.datumapis.com-viewer

Why

The networking.datumapis.com-location-admin role existed in isolation — it wasn't inherited by the viewer or admin role, so even org owners with full networking access were getting Forbidden when trying to list locations. This blocked workload creation since the compute webhook lists locations to validate city codes.

The fix follows the existing pattern (connector-viewer, gateway-viewer, domain-viewer) by splitting read and write access into separate roles and pulling the viewer into the networking-viewer hierarchy.

🤖 Generated with Claude Code

scotwells and others added 2 commits May 20, 2026 13:04
The location-admin role existed in isolation — nothing inherited it,
so even org owners with full networking access were forbidden from
listing locations. Adds a read-only location-viewer role and wires
it into networking-viewer so the full viewer/admin hierarchy has
location read access.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Location resources are expected to move out of the networking group
soon; grant location view access via assignable org roles directly
rather than through the networking-viewer inheritance chain.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant