ENH Persist API-created targets - #3
Closed
behnam-o wants to merge 1 commit into
Closed
Conversation
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: e83115c3-5e73-489c-a39d-bd50eadc9af0
Owner
Author
|
Closing this fork-local PR; the change is now proposed against the upstream repository. |
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
1 participant
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.
Problem
Targets created through the backend are only registered in memory, so they disappear when the backend restarts.
Solution
Persist non-secret target definitions in the configured PyRIT database and restore them during startup. API keys are stored in an optional Azure Key Vault configured with
target_secret_key_vault_url; when durable storage is unavailable, the UI warns that the target will remain memory-only.