Skip to content

chore: add environment variables to Bicep for local development setup #535

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: dev
Choose a base branch
from

Conversation

Priyanka-Microsoft
Copy link
Contributor

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?

  • Yes
  • No

Golden Path Validation

  • I have tested the primary workflows (the "golden path") to ensure they function correctly without errors.

Deployment Validation

  • I have validated the deployment process successfully and all services are running as expected with this change.

What to Check

Verify that the following are valid

  • I have built and tested the code locally and in a deployed app
  • For frontend changes, I have pulled the latest code from main, built the frontend, and committed all static files.
  • This is a change for all users of this app. No code or asset is specific to my use case or my organization.

Other Information

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants