Ken Schlobohm
Ken Schlobohm
Thanks @jiasli, I wasn't aware this was a known issue My workflow was something like: 1. `az ad app update --help` 2. try out the command (it failed) 3. read...
I've been building a project with azd that includes a production ready environment and found that high availability is another scenario that uses multiple resource groups. In that scenario I...
I was previously using the environment name to trigger the conditional bicep behavior as you're describing but I started preferring parameters to control, and describe, the outcome vs the magic...
Deploying to two azure locations within the same resource group works for my scenario. Thanks @karolz-ms
That worked for me. I think the help text says this should also work `azd env new staging` where staging is the same as `azd env new `
@karolz-ms this surfaced again and the response code was HTTP 202 so I looked at the message closer. It seems the error log was captured in kudu. ``` { "Message":...
Sorry for the confusion, when I found the HTTP 202 code I thought it was another instance of the same error. The 202 status does not seem to be related...
Thanks @rafikiassumani-msft the video was good content and provided good guidance! My goal was to have a generated client that uses intelligent method naming so I could more clearly associate...
Also blocked with a URL of the pattern similar to: ``` https://dev.azure.com/mydevOpsOrgName/myProjectName ```
@weikanglim +1 for WSL experience