feat(policy)!: add namespace field to RegisteredResource proto#3110
feat(policy)!: add namespace field to RegisteredResource proto#3110alkalescent merged 3 commits intomainfrom
Conversation
Signed-off-by: Krish Suchak <suchak.krish@gmail.com>
Summary of ChangesHello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request introduces foundational namespace support for policy-related registered resources. It modifies core protobuf definitions to include namespace fields, allowing resources to be scoped and filtered by namespace. This change is a prerequisite for broader namespace-aware functionality, laying the groundwork for more granular policy management. Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Changelog
Ignored Files
Activity
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Proto fields expand, Namespace now holds the new key, Policies align. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request introduces a namespace field to the RegisteredResource protobuf message and updates related request messages to support namespacing, which is a good step towards multi-tenancy for registered resources.
I have one suggestion regarding protobuf field numbering in CreateRegisteredResourceRequest for better maintainability.
Additionally, the pull request summary mentions adding a namespace field to RegisteredResourceValue, but this change is not present in the current patch. This might be intentional and planned for a future PR, but it's worth clarifying if RegisteredResourceValue should have its own namespace field for cases where it's retrieved without its parent RegisteredResource object being fully populated.
Benchmark results, click to expandBenchmark authorization.GetDecisions Results:
Benchmark authorization.v2.GetMultiResourceDecision Results:
Benchmark Statistics
Bulk Benchmark Results
TDF3 Benchmark Results:
|
Signed-off-by: Krish Suchak <suchak.krish@gmail.com>
Benchmark results, click to expandBenchmark authorization.GetDecisions Results:
Benchmark authorization.v2.GetMultiResourceDecision Results:
Benchmark Statistics
Bulk Benchmark Results
TDF3 Benchmark Results:
|
Benchmark results, click to expandBenchmark authorization.GetDecisions Results:
Benchmark authorization.v2.GetMultiResourceDecision Results:
Benchmark Statistics
Bulk Benchmark Results
TDF3 Benchmark Results:
|
🤖 I have created a release *beep* *boop* --- ## [0.17.0](protocol/go/v0.16.0...protocol/go/v0.17.0) (2026-03-05) ### ⚠ BREAKING CHANGES * **policy:** add namespace field to RegisteredResource proto ([#3110](#3110)) ### Features * **policy:** add namespace field to RegisteredResource proto ([#3110](#3110)) ([04fd85d](04fd85d)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: opentdf-automation[bot] <149537512+opentdf-automation[bot]@users.noreply.github.com>
## Summary - Adds namespace support to Registered Resources in service layer, DB queries, and migrations - Updates identifier library for registered resource value namespace handling - Adds integration and unit tests for namespace-scoped registered resources **Depends on #3110** (proto changes) being merged first. This is part 2 of splitting #3106 into two PRs. ## Test plan - [x] Integration tests pass for registered resources with namespace - [x] Unit tests pass for identifier library changes - [x] Migration applies cleanly - [x] Existing registered resource functionality unaffected --------- Signed-off-by: Krish Suchak <suchak.krish@gmail.com>
Summary
namespacefield toRegisteredResourceandRegisteredResourceValueproto messagesListRegisteredResourcesRequestwith namespace filter fieldThis is part 1 of splitting #3106 into two PRs. Part 2 (service/lib changes) depends on this being merged first.
Test plan