Closed mawah closed 5 years ago
Found the problem. I'd downloaded my connection string from my Azure Functions app as follows:
func azure functionapp fetch-app-settings <my azure functions app name>
...and this pulled down several other values to my local.settings.json
file, including:
"FUNCTIONS_WORKER_RUNTIME": "node",
This value is the type of Azure Functions app I created in Azure. (Python was not listed as an option when I created my Azure Functions resource: my choices during deployment were .NET and Node.js, I think.) I manually changed the runtime value from node
to python
and was able to get things working.
Is there a way to create an Azure Functions cloud resource with a Python runtime, for compatibility with Python functions I create using Azure Functions Core Tools (and the samples here)?
@mawah Very sorry for the late response. In V2 functions, Python is in preview but if you use the latest Azure function runtime, you'll see Python listed. Please read the following pages:
I'm closing this but please feel free to open if there are any issues
I am struggling to test one of the samples from this repository, eventhub-trigger-table-out-bindings, in Azure Functions Core Tools. It appears that I've successfully populated the connection strings in
local.settings.json
and resource names infunction.json
: the function loads without any errors. However, I get a message I don't understand staying:It appears there is some distinction between "functions" and "job functions" (I know nothing about it), but this error message doesn't explain it and seems maybe intended for a different programming language? I don't know why the
__init__.py
file in eventhub-trigger-table-out-bindings doesn't qualify as a job function nor how to fix the problem. (It appears that there is a problem, because nothing happens when I run the associatedsend-event.py
script to trigger the function.)Here is the full output displayed when I launch local execution with Azure Functions Core Tools:
Any advice appreciated!