You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Output from azd version
Run azd version and copy and paste the output here:
azd version 1.4.3 (commit d165bd2)
Describe the bug
When deploying a container app, azd provision or azd up crashes if the language property is not set. This property should be irrelevant in the case of building a Docker image.
This is similar to #1645. We don't currently handle a language:none scenario (we probably should though...as the language doesn't matter for ACA hosted apps).
That said, at the very least/in the meantime, we should have better error handling here.
IIRC, we used to have a better error message for this since #2066 (language property must be set) but since our internal implementation push to make every component an application lifetime registration, we've somewhat lost visibility into how these conditions should be handled due to the complexity introduced with dependency injection. Not to say that it can't be fixed easily even in our current DI model, but it is certainly harder to spot.
A nil error panic is certainly something we should avoid completely.
Output from
azd version
Run
azd version
and copy and paste the output here:azd version 1.4.3 (commit d165bd2)
Describe the bug
When deploying a container app,
azd provision
orazd up
crashes if thelanguage
property is not set. This property should be irrelevant in the case of building a Docker image.Crash log:
To Reproduce
Relevant extract from
azure.yaml
Expected behavior
Language should be optional for containers, and azd should not crash.
Environment
MacOS 14.0
The text was updated successfully, but these errors were encountered: