@Kirkwood Williams Thanks for getting back. Regarding your query about the requirements.txt:
The requirements.txt file contains the list of Python packages the system installs when it publishes to Azure. When you're ready to publish, make sure that all your publicly available dependencies are listed in the requirements.txt file.
Note: The runtime library version is fixed by Azure, and it can't be overridden by requirements.txt. The azure-functions
entry in requirements.txt is only for linting and customer awareness. More info here.
You can simply remove the azure-functions
and test your function app. See the below screenshot from my machine.
requirements.txt
I am able to successfully trigger the function app without any entry in the requirements.txt:
However, If your app has any dependencies on a few of the library packages then you can add those to the requirements.txt. Then you can use the remote build
option and deploy your code to Azure. When you use remote build, dependencies that are restored on the server and native dependencies match the production environment. This results in a smaller deployment package to upload. Use remote build when you're developing Python apps on Windows.
Dependencies are obtained remotely based on the contents of the requirements.txt file. Remote build is the recommended build method. By default, Core Tools requests a remote build when you use the following func azure functionapp publish
command to publish your Python project to Azure.
func azure functionapp publish <APP_NAME>
Hope this helps.