microsoft / microsoft/azurechat
Failure: Build & deploy Next.js app to Azure Web App
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.4k
- Forks
- 1.3k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 1
Description
Hello,
- I stood up an instance of Azure Chat without issue in late 2023.
- I decided to do a clean implementation today so I disconnected my 2023 fork and archived my repository.
- I forked Azure Chat again, deployed the Azure resources, etc.
- Now when I try to deploy my code from Github to Azure, I get the following failure error: "Login failed with Error: Not all parameters are provided in 'creds'. Double-check if all keys are defined in 'creds': 'clientId', 'clientSecret', 'tenantId'.. Double check if the 'auth-type' is correct."
- I've double, triple, and quadruple-checked my app registration, service principal JSON output and secrets in Github, etc.
I can't figure out why this worked so smoothly back in 2023 but now I'm running into problems. Any assistance will be greatly appreciated.
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 reviewing the GitHub-to-Azure deployment configuration, the service principal JSON, the GitHub secrets, and the configured auth-type. Reproduce the reported login failure and verify the deployment can authenticate with clientId, clientSecret, and tenantId. The issue is resolved when the forked Next.js app deploys successfully to Azure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, next.js, typescript
- Domain
- authentication, ci-cd, cloud, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100