chore: add environment variables to Bicep for local development setup #535
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.
Purpose
This pull request expands the outputs in the infrastructure Bicep files to expose additional configuration values related to Azure OpenAI, Azure Search, and CosmosDB resources. These outputs will make it easier for downstream services and environments to access key parameters for deployment and integration.
Infrastructure output enhancements:
infra/deploy_app_service.bicep
: Added outputs for various Azure OpenAI configuration values (system messages, prompts, model, resource), Azure Search settings (index, service, query type, vector fields), and CosmosDB feedback enablement flag.infra/main.bicep
: Propagated the new outputs from the app service and CosmosDB modules, including OpenAI prompts and settings, search service/index, CosmosDB configuration, and AI agent endpoint details.Does this introduce a breaking change?
Golden Path Validation
Deployment Validation
What to Check
Verify that the following are valid
Other Information