Repository navigation
feat(gateway): admin applications API and RLS hardening - #14
Merged
Merged
Conversation
devXyi
marked this pull request as ready for review
October 16, 2026 07:28
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
Add administrator-only read endpoints for submitted access applications, plus PostgreSQL API-role hardening.
Changes
GET /admin/applicationswith bounded pagination andGET /admin/applications/:refwith reference validation.applications:readpermission foradminonly.users,assets, andapplications; revoke grants foranonandauthenticatedif present.golang.org/x/netto v0.60.0.Validation
GitHub Actions on the latest commit passed: Go vet, race-enabled tests and
govulncheck; Rust tests andcargo audit; Python engine tests andpip-audit; prexus_core/Raksha tests; offline air-gap tests; full-history secret scan; and all four CodeQL language analyses.Security caveat
The RLS hardening is best-effort if the runtime DB role does not own the tables; production must apply/verify it through a privileged migration role before exposing the tables through a database API. No merge or deployment was performed.