Repository navigation
P4.2 PR2: Traffic Hooks admin panel, versions/rollback and dry-run UI - #435
Merged
Merged
Conversation
…y-run UI (P4.2 PR2)
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.
P4.2 PR2: operator UI for the tampering hooks, built on the API merged in #434. No backend change, no new endpoint.
The feature stays off unless
ARTEX_TAMPER_HOOKS_ENABLED=1, and the tab is operator-only, like the rest of the traffic tooling.enabled:falseand the toggle is a separate deliberate action.dangerouslySetInnerHTML, noeval).tr.jsonandzh-CN.json, English fallback for the rest.Tests:
web/scripts/tamper-hooks.test.mjscovers response parsing, dry-run input derivation from a captured exchange, matcher line parsing, request-phase matcher filtering, and trace decoding with masked-field detection;test:i18nchecks key parity;tsc --noEmitis clean.