Deploying through VS Code shows Warmup api

[asavaritayal]

From @priyaananthasankar on September 26, 2018 5:25

Linux Consumption Plan preview.

Created a simple HTTP trigger and deployed into azure function app through VS Code. It worked fine.
Added another HTTP trigger method that used Cosmos DB extension and redeployed to the same function app through VS Code. These were the output logs:

10:13:41 PM Honeydukes: Starting deployment...
10:13:42 PM Honeydukes: Uploading zip package to storage container...
10:18:26 PM Honeydukes: Starting deployment...
10:18:27 PM Honeydukes: Uploading zip package to storage container...
Deployment to "Honeydukes" completed.
HTTP Trigger Urls:
WarmUp: https://honeydukes.azurewebsites.net/api/WarmUp

---

The portal also showed up WarmUp API and when GET request was sent to it, it responded 200OK Warmup complete. None of my function API's got deployed.

Copied from original issue: Azure/azure-functions-python-worker#207

[ejizba]

@priyaananthasankar what exactly was your "expected" vs "actual" behavior? Does everything show up correctly after you restart the function app? We have a known issue where triggers may not be getting synced after a deploy. See #657 (which has been fixed, but not released yet)

[balag0]

This is a bug in the functions runtime. tracked by Azure/azure-functions-host#3541

[mathewc]

My fix is in, and @balag0 is planning on deploying the update in the next day or two. After that is deployed let's rerun these scenarios and verify the issue is fixed.

[mathewc]

I closed #668, but I'll leave this one open until final verification.

[asavaritayal]

Closing issue as this seems to be resolved now.