feat(policy): namespace Registered Resources#3106
Conversation
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 a significant architectural enhancement by implementing namespacing for Registered Resources. This change allows for better organization and isolation of resources, addressing potential naming conflicts and improving multi-tenancy support. The modifications span across data models, database schema, API contracts, and internal logic, ensuring a robust and backward-compatible solution for managing both new namespaced and existing legacy resources. 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. A resource, once alone, Now finds a home, a namespace known. No longer lost, but neatly bound, In order, logic can be found. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request introduces namespacing for Registered Resources, a significant and well-implemented feature. The changes are comprehensive, touching the database schema, queries, application logic, and API definitions, while maintaining backward compatibility for legacy resources. The database migration and integration tests are particularly well-executed.
I have two main points of feedback. First, there's an opportunity to reduce code duplication in the FQN parsing logic for better maintainability. Second, there is a potential N+1 query performance issue in the same-namespace enforcement logic that should be addressed by batching database queries. Overall, this is a strong pull request, and addressing the performance concern is recommended.
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:
|
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:
|
Proposed Changes
Checklist
Testing Instructions