feat: add OPENAI_API_KEY to frontEnd module configuration#283
feat: add OPENAI_API_KEY to frontEnd module configuration#283
Conversation
There was a problem hiding this comment.
Pull request overview
Adds an OPENAI_API_KEY application setting to the frontEnd App Service module so the frontend deployment can receive an OpenAI key via configuration.
Changes:
- Add
OPENAI_API_KEYto thefrontEndmoduleappSettingsininfra/main.bicep.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| } | ||
| { | ||
| name: 'OPENAI_API_KEY' | ||
| value: mcpOpenAiApiKey |
There was a problem hiding this comment.
This app setting uses mcpOpenAiApiKey directly, but the rest of the template consistently uses the normalized *Var value (e.g., mcpOpenAiApiKeyVar for OPENAI_API_KEY in the orchestrator settings). Using the *Var here would keep conventions consistent and avoids confusion given the parameter is described as "used by the MCP server" while it's now also consumed by the frontend; consider switching to mcpOpenAiApiKeyVar and/or clarifying the parameter naming/description to reflect shared use.
| value: mcpOpenAiApiKey | |
| value: mcpOpenAiApiKeyVar |
No description provided.