A developer CLI that reduces the time it takes for you to get started on Azure. The Azure Developer CLI (azd) provides a set of developer-friendly commands that map to key stages in your workflow - code, build, deploy, monitor, repeat.
Output from azd version
azd version 1.8.0 (commit 8246323c2472148288be4b3cbc3c424bd046b985)
Describe the bug
When deploying a JavaScript Azure Function with AZD, the installation of dependencies and build of the app is done remotely with Oryx.
When deploying the Functions, AZD reports a successful deployment as the zip upload succeeds, but the Function app is not deployed if the Oryx build fails and there's no easy way to detect and debug that when it happens.
cd packages/api && npm rm typescript => We remove the typescript tool from the Functions API, causing the build to fail
azd deploy => Deployment success, but no Function app is actually deployed
Expected behavior
AZD should not report a successful deployment if Oryx build fails, or at least provide a way to check if an issue occurred and show the actual error logs from the Oryx build.
Output from
azd version
azd version 1.8.0 (commit 8246323c2472148288be4b3cbc3c424bd046b985)Describe the bug When deploying a JavaScript Azure Function with AZD, the installation of dependencies and build of the app is done remotely with Oryx.
When deploying the Functions, AZD reports a successful deployment as the zip upload succeeds, but the Function app is not deployed if the Oryx build fails and there's no easy way to detect and debug that when it happens.
To Reproduce
cd packages/api && npm rm typescript
=> We remove the typescript tool from the Functions API, causing the build to failazd deploy
=> Deployment success, but no Function app is actually deployedExpected behavior AZD should not report a successful deployment if Oryx build fails, or at least provide a way to check if an issue occurred and show the actual error logs from the Oryx build.
Environment Information on your environment: