{{ message }}
Repository navigation
Conversation
This branch has not been deployed
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
This change implements the foundational authorization privilege extraction system for DocumentDB, introducing a new
get_required_privileges()function that analyzes MongoDB commands and returns the required resource privileges needed to execute them. This is the first step in building a MongoDB-compatible Role-Based Access Control (RBAC) system.Overview
This CR introduces a static privilege extraction system that:
Current Scope: Implements extraction for
findcommands as a proof-of-concept. Future commands will follow the same pattern.Test Coverage (authorization_get_required_privileges_find.sql - 16 tests)
PostgreSQL Interface:
command_get_required_privileges()- PG_FUNCTION_INFO_V1 wrapper{ "ok": 1.0, "canDeterminePrivileges": true, "privileges": [ { "resource": {"db": "test", "collection": "users"}, "actions": ["find"] } ] }canDeterminePrivileges: falsefor unsupported commandsPositive Test Cases: