For function apps using FWPC > 1 and using blueprints, the second worker does not get the metadata request. In the load request, the worker uses the function directory sent from the host. This works for functions apps without blueprints since the func dir is always /home/site/wwwroot. For blueprints, the function dir is /home/site/wwwroot/. So in the load request, the worker tries to find function_app.py in /home/site/wwwroot/ and it fails indexing.
Fix is to always use /home/site/wwwroot for v2 programming model
Fixes #
PR information
[ ] The title of the PR is clear and informative.
[ ] There are a small number of commits, each of which has an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[ ] If applicable, the PR references the bug/issue that it fixes in the description.
[ ] New Unit tests were added for the changes made and CI is passing.
Description
This fixes a bug introduced in https://github.com/Azure/azure-functions-python-worker/pull/1446.
For function apps using FWPC > 1 and using blueprints, the second worker does not get the metadata request. In the load request, the worker uses the function directory sent from the host. This works for functions apps without blueprints since the func dir is always /home/site/wwwroot. For blueprints, the function dir is /home/site/wwwroot/. So in the load request, the worker tries to find function_app.py in /home/site/wwwroot/ and it fails indexing.
Fix is to always use /home/site/wwwroot for v2 programming model
Fixes #
PR information
Quality of Code and Contribution Guidelines