feat(policy): List obligation triggers rpc

[c-r33d]

Proposed Changes

1.) Implement the ListObligationTriggers RPC, which allows a user to list obligation triggers globally. The user can specify an optional namespace filter.
2.) Add NULLIF check for UUID casts to avoid errors do to early parameter binding optimizations.

Checklist

• I have added or updated unit tests
• I have added or updated integration tests (if appropriate)
• I have added or updated documentation

Testing Instructions

[gemini-code-assist]

Summary of Changes

Hello @c-r33d, I'm Gemini Code Assist¹! 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 new API endpoint to list obligation triggers, providing a flexible way to query these triggers across the system. It enables filtering by namespace and supports pagination for managing result sets. The changes span the database layer, service implementation, and include thorough testing to ensure robustness and correctness.

Highlights

• New RPC Endpoint: Implemented the ListObligationTriggers RPC, allowing users to retrieve a list of obligation triggers globally.
• Namespace Filtering: The new RPC supports optional filtering of obligation triggers by namespace ID or Fully Qualified Name (FQN).
• Pagination Support: The ListObligationTriggers RPC includes pagination capabilities, enabling efficient retrieval of large datasets.
• Database Query Implementation: Added a new SQL query (listObligationTriggers) to efficiently fetch obligation triggers from the database, incorporating filtering and pagination logic.
• Comprehensive Integration Tests: Extensive integration tests have been added and updated to cover various scenarios for listing obligation triggers, including different filter combinations, pagination, and multi-namespace setups.
• Test Suite Enhancements: The ObligationTriggersSuite in integration tests was enhanced with new helper functions for creating unique triggers, validating responses, and improved cleanup mechanisms for obligation values.

Using Gemini Code Assist

The 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 /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

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 .gemini/ folder in the base of the repository. Detailed instructions can be found here.

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 trigger list, so grand, By namespace, at command. With pages turning, fast and free, Policy's order, for all to see.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request implements the ListObligationTriggers RPC, including the database query, service logic, and comprehensive integration tests. The changes are well-structured and the tests cover various scenarios, including filtering and pagination. I've identified a performance issue in the SQL query for listing triggers and provided a suggestion for optimization. Overall, this is a solid implementation.

[github-actions]

Benchmark results, click to expand

Benchmark authorization.GetDecisions Results:

Metric	Value
Approved Decision Requests	1000
Denied Decision Requests	0
Total Time	177.117799ms

Benchmark authorization.v2.GetMultiResourceDecision Results:

Metric	Value
Approved Decision Requests	1000
Denied Decision Requests	0
Total Time	101.419016ms

Standard Benchmark Metrics Skipped or Failed

Bulk Benchmark Results

Metric	Value
Total Decrypts	100
Successful Decrypts	100
Failed Decrypts	0
Total Time	357.589632ms
Throughput	279.65 requests/second

TDF3 Benchmark Results:

Metric	Value
Total Requests	5000
Successful Requests	5000
Failed Requests	0
Concurrent Requests	50
Total Time	38.723773236s
Average Latency	385.218823ms
Throughput	129.12 requests/second

NANOTDF Benchmark Results:

Metric	Value
Total Requests	5000
Successful Requests	5000
Failed Requests	0
Concurrent Requests	50
Total Time	27.168322884s
Average Latency	270.707433ms
Throughput	184.04 requests/second

[github-actions]

Benchmark results, click to expand

Benchmark authorization.GetDecisions Results:

Metric	Value
Approved Decision Requests	1000
Denied Decision Requests	0
Total Time	169.050652ms

Benchmark authorization.v2.GetMultiResourceDecision Results:

Metric	Value
Approved Decision Requests	1000
Denied Decision Requests	0
Total Time	98.602922ms

Standard Benchmark Metrics Skipped or Failed

Bulk Benchmark Results

Metric	Value
Total Decrypts	100
Successful Decrypts	100
Failed Decrypts	0
Total Time	358.272843ms
Throughput	279.12 requests/second

TDF3 Benchmark Results:

Metric	Value
Total Requests	5000
Successful Requests	5000
Failed Requests	0
Concurrent Requests	50
Total Time	38.804997283s
Average Latency	386.347056ms
Throughput	128.85 requests/second

NANOTDF Benchmark Results:

Metric	Value
Total Requests	5000
Successful Requests	5000
Failed Requests	0
Concurrent Requests	50
Total Time	27.023404616s
Average Latency	269.52539ms
Throughput	185.02 requests/second

[github-actions]

Benchmark results, click to expand

Benchmark authorization.GetDecisions Results:

Metric	Value
Approved Decision Requests	1000
Denied Decision Requests	0
Total Time	177.081669ms

Benchmark authorization.v2.GetMultiResourceDecision Results:

Metric	Value
Approved Decision Requests	1000
Denied Decision Requests	0
Total Time	89.849648ms

Standard Benchmark Metrics Skipped or Failed

Bulk Benchmark Results

Metric	Value
Total Decrypts	100
Successful Decrypts	100
Failed Decrypts	0
Total Time	359.780526ms
Throughput	277.95 requests/second

TDF3 Benchmark Results:

Metric	Value
Total Requests	5000
Successful Requests	5000
Failed Requests	0
Concurrent Requests	50
Total Time	40.372331182s
Average Latency	402.521545ms
Throughput	123.85 requests/second

NANOTDF Benchmark Results:

Metric	Value
Total Requests	5000
Successful Requests	5000
Failed Requests	0
Concurrent Requests	50
Total Time	28.382200913s
Average Latency	282.652754ms
Throughput	176.17 requests/second