Azure-Samples / Azure-Samples/azure-devops-release-notes
UserDomain can't be added to app settings via Arm or ADO
- Lingua principale
- C#
- Stelle
- 79
- Fork
- 31
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Descrizione
> Please provide us with the following information:
> ---------------------------------------------------------------
### This issue is for a: (mark with an `x`)
```
- [x ] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)
```
### Minimal steps to reproduce
>
deploy to azure using arm template with userdomain defined as a parameter
### Any log messages given by the failure
>The data is not valid (Invalid or not allowed environment key name: UserDomain
### Expected/desired behavior
> add userdomain as an app setting to web app
### OS and Version?
> Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)
### Versions
>
### Mention any other details that might be useful
I tried deploying using custom template and azure devops, both failed with the same error. removing the param and app setting from the template deploys the app successfully.
> ---------------------------------------------------------------
> Thanks! We'll be in touch soon.
Guida per i contributori
Apri la guida per i contributori
Direzione di ricerca
Start by reproducing the deployment with an ARM template and Azure DevOps, using UserDomain as a parameter and app setting. Inspect the validation path that rejects the environment key; done when the app setting deploys successfully through both reported paths without the invalid-key error.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- azure
- Ambito
- cloud, devops
- Tipo di issue
- Bug
- Difficoltà
- 3/5
- Tempo stimato
- 1-2 giorni
- Stato di attività
- Ferma
- Chiarezza
- Abbastanza chiara
- Idoneità per principianti
- 35/100