refactor(infra): use Key Vault reference for chat system prompt#184
Merged
willvelida merged 1 commit intomainfrom Mar 15, 2026
Merged
refactor(infra): use Key Vault reference for chat system prompt#184willvelida merged 1 commit intomainfrom
willvelida merged 1 commit intomainfrom
Conversation
Signed-off-by: Will Velida <willvelida@hotmail.co.uk>
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
Updates the chat-api Bicep template to reference the system prompt from Key Vault instead of storing it as a plain-text App Configuration value.
Changes
chatSystemPromptBicep parameter (which had the old plain-text prompt as a default)chatSystemPromptSettingApp Configuration resource to use a Key Vault reference, matching the existingAnthropicApiKeypatternContext
The hardened system prompt was already uploaded to Key Vault via the CLI. This PR brings the Bicep template in sync with the actual Azure state.
Part of ASI01 (Agent Goal Hijack) — plan:
docs/plans/2026-03-13-asi01-harden-system-prompt.md