Repository navigation
prism-cli 1.19.1: the setup gate's 10 s re-check reads only what steps 1 and 2 need - #119
Merged
Merged
Conversation
…s 1 and 2 need - GET /api/security-agent/gate?repo=<id>: one repo from the last full answer, from the AWS and aws connect files, AWS_PROFILE and the setup records. No git, no result files, no repo scan. - The page polls it while step 1 or 2 is on screen and the tab is visible, redraws only on change, and loads the full answer once the step passes. - A redraw keeps the pending re-check (the heatmap's 3 s loads used to push it back). - Unit test: the re-check spawns no git process; e2e GATE6: the wait uses the light endpoint.
✅ PRISM Eval Gate -- PASSScore: 0.93 | Findings: 4 (0 high, 0 medium) Summary: The change is sound. It adds a light gate re-check endpoint with strict id validation against a known-repo allowlist and 404 handling. It has no blocking issues, only low-severity notes on the git-tra
✅ Secret scan -- no credentials found in this PR's commits. |
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.
prism-cli 1.19.1. Follow-up to #118: the setup gate's 10 s re-check no longer scans every repo.
What changes
While step 1 or 2 is on screen, the card checked again every 10 s with the full
GET /api/security-agent. That runsgit rev-parse HEADandgit ls-filesand reads every repo's result files, for every discovered repo. On a machine with about 43 repos, that is real work every 10 s.GET /api/security-agent(all repos, git, result files)GET /api/security-agent/gate?repo=<id>: the picked repo only, from the AWS and aws connect files,AWS_PROFILEand the setup records. No git, no result files, no repo scanSame action allowlist, listener, token and CSP. The endpoint is read-only, makes no AWS call, and returns masked account ids only.
Tests
npm test(aws guard): 875/875.gitplaced first on PATH), lists no repos, and makes no AWS call.npm run docs:check: 0 problems./api/security-agent/gate, and full answers come only with page loads.Docs: USER_GUIDE (what the re-check reads); CLI-REFERENCE version.