Azure portal not showing any functions, when deployed from zip with github or az CLI about azure-functions HOT 12 OPEN

I'm facing the same issue with a Python function. Deployment works as expected on VSCode, but the same thing happens when using azure-cli or GH Actions (also, besides the function names not appearing in the Azure Portal, my HTTP trigger functions 404)

from azure-functions.

I am facing the same issue here. Whenever I add some code to interact with a database, the function in VSCode shows that it deployed, but I see nothing when I visit my Azure portal. When I remove/comment out the database interaction code, everything seems to work fine. Did someone find a workaround for this? I am using NodeJS btw!
@bhagyshricompany

This screenshot from the logs shows that the function was found but it could not be loaded. I have no idea why.

from azure-functions.

Thanks for reporting.can you try with azure portal option and please share the func app name,invocation id,timestamp,logs screenshot..Thanks

from azure-functions.

I'm facing the same issue with a Python function. Deployment works as expected on VSCode, but the same thing happens when using azure-cli or GH Actions (also, besides the function names not appearing in the Azure Portal, my HTTP trigger functions 404)

Exactly the same. Function App not appear at all. OTOH, I'm with TimerTrigger Python Function.

from azure-functions.

I had the issue with our Functions app (dotnet-isolated) after upgrading from dotnet7 to dotnet8. I tried a variety of fixes, including changing some versions of some of the dependent Azure Functions SDK projects as I'd seen some threads indicate that was their fix. Nothing was working.

Upon attempting to just deploy from VS, I found that the deployment worked. Weird. So I went and grabbed the deployed artifacts from our AzRepos pipeline, and the VS deployed package, and diff'd them (Beyond Compare FTW).

Most of the differences were seemingly noise/meaningless, except for one thing. The worker.config.json file that is built was deployed from our Pipeline as {WorkerRoot}<our-entry-assembly-name-without-extension>, but when published from VS was simply dotnet. I tossed this into our deployment yaml (where is our build artifact), for right before the deployment task:

  - task: PowerShell@2
    name: update_worker_config
    displayName: 'Update Worker Config'
    inputs:
      targetType: 'inline'
      script: |
        $configPath = "$(Pipeline.Workspace)/build/output/<artifact-name>/worker.config.json"
        $config = Get-Content -Path $configPath -Raw | ConvertFrom-Json
        $config.description.defaultExecutablePath = 'dotnet'
        $config | ConvertTo-Json | Set-Content -Path $configPath

And it worked!

Interestingly enough however, I just looked at the artifacts for our latest build pipeline (only 1 non-relevant code file has changed in the mean time), and it appears that the value now being artifacted IS simply dotnet, so looks like this may have been resolved with an update, though I don't immediately see any recently released SDK updates for AzFunctions 🤷‍♂️.

from azure-functions.

I'm facing the same issue, but I cannot understand if it's a misconfiguration.
Mine is an http triggered python function

from azure-functions.

have the same

from azure-functions.

@tostringtheory , I am using Github workflows and have verified the worker.config.json in the pipeline functions artifact, but that already contains "defaultExecutablePath": "dotnet". So, I guess that's not the original reason for my issue...

from azure-functions.

I have similar issue with NodeJS function.
When I deploy to Consumption Plan - everything works well. But if I create "App service plan" (I need Always On feature) function and deploy same code - I cannot see my function in list.
Any ideas what could be the reason?

from azure-functions.

Ok, the reason was I've been creating Azure function resources in Europe North region. Once I've moved to Europe West everything worked for me. That's weird...

from azure-functions.

Ok, the reason was I've been creating Azure function resources in Europe North region. Once I've moved to Europe West everything worked for me. That's weird...

Use a containerized environment if you can.

from azure-functions.

Any feedback on this? Also had this issue but it seems to have fixed on itself

from azure-functions.