[Issue] Azure Functions deployment reports success, but function not deployed because Oryx build failed

[sinedied]

• Make sure you've installed the latest version using instructions in the wiki

Output from azd version
azd version 1.8.0 (commit 8246323)

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

1. Git clone this repo: https://github.com/Azure-Samples/serverless-chat-langchainjs/
2. cd packages/api && npm rm typescript => We remove the typescript tool from the Functions API, causing the build to fail
3. 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.

Environment
Information on your environment:
* Language name and version: TypeScript
* IDE and version : VS Code

[rajeshkamal5050]

@hemarina does your fix for #3260 also covers this one? cc @weikanglim

[hemarina]

@rajeshkamal5050 It won't work for function app because deployment status api currently only support Linux web apps.

[sinedied]

I'm using Linux Functions and I still ran into this issue again.
This is quite problematic as it reports deployment to be successful, and may fail on post deployment tasks (if there are any) making the users confused and the debugging not easy.

Any updates regarding this?

[spboyer]

Investigated the current codebase. This is likely still an issue for regular (non-Flex Consumption) Function Apps.

Root cause: the zipdeploy client (pkg/azsdk/zip_deploy_client.go) considers deployment successful when the poller completes (Complete == true) but does not validate the deployment Status field. A deployment can complete with a logically failed status.

Flex Consumption path (funcapp_host_client.go) explicitly checks for cancelled/failed/partial/conflict statuses and correctly reports failures.

Recent PR #6748 added remoteBuild for Flex Consumption but did not address the regular zipdeploy status validation gap.