microsoft / microsoft/azurechat
Web app ignores the AZURE_OPENAI_BASE_PATH setting suggested in another issue #170
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.4k
- Forks
- 1.3k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 1
Description
This is related to:
AOI Endpoint URL Creation - Doesn't work with an API-M / App Gateway or other interceptor. #170
I imported to APIM the AOAI model deployed with this azure chat web app. Then, I set the AZURE_OPENAI_BASE_PATH variable as per recommendation from issue above, but the web app is ignoring that setting. I used this workaround last year when I deployed this same azure chat web app and it worked fine. I wonder if something has changed in the code that does not allow this APIM integration.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how the AZURE_OPENAI_BASE_PATH setting is read and how the AOAI endpoint URL is created, using issue #170 as the comparison point. Confirm whether the configured base path is used for APIM or App Gateway requests; done means the web app routes requests through that configured path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, typescript
- Domain
- api, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100