Open gabrieljoelc opened 1 year ago
@gabrieljoelc I don't know specifically about crtl c'ing when the sync is underway. But I think there are issues with azure-functions-core-tools. Our application was deploying and syncing fine from local scripts on windows machines. But on the pipelines (linux image) the tool would report successful sync but then there would be no functions in the app. Upgrading azure-functions-core-tools to v4 (which seems to introduce dependency on dotnet sdk) seems to have solved the problem. TLDR be suspicious of azure-functions-core-tools v3 output when publishing
I have been using
func functionapp publish
to deploy to a Linux Consumption Function App:which normally outputs all the triggers when the deployment is complete:
One of the times I was running it, I Ctrl+C'd during the "Sync triggers..." output:
Now when I run the same command, I doesn't output the triggers and show this:
The triggers fail to sync and the portal shows I have no triggers.
Things I've tried:
az login
~/.azure
directoryUpdate 1
I checked the
WEBSITE_RUN_FROM_PACKAGE
setting in the function app and it does have the correct URL of the latest release. I curl the URL, downloaded the file as a zip, and verified that it contains the built application code. š¤·Is it something related to the SIGINT breaking the CLI so it can't bump the
azure-webjobs-hosts/synctriggers/my-linux-consumption-func-app/last
blob anymore or something?