You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a basic Pwsh HTTP Trigger here made using the AzFx extension. I have the Azurite ext installed and set "AzureWebJobsStorage": "UseDevelopmentStorage=true" in local.settings.json. I cannot debug/run the function as it keeps waiting for func: host start. Doing "AzureWebJobsStorage": "" will work. Starting Azurite Blob Service myself will work as well.
There are some inconsistencies between how different runtimes handle this:
In Python, this works fine
In Node, it will ask if Azurite is installed or running first
Proposition: a way to attempt to start Azurite when debugging/starting func host before telling the user it's not installed. There is a VS Code command for that: vscode.commands.executeCommand('azurite.start')
This way we can standardize how all runtimes handle this case - as not all triggers will not use Azurite as well
The text was updated successfully, but these errors were encountered:
On VS Code Desktop
I have a basic Pwsh HTTP Trigger here made using the AzFx extension. I have the Azurite ext installed and set "AzureWebJobsStorage": "UseDevelopmentStorage=true" in local.settings.json. I cannot debug/run the function as it keeps waiting for func: host start. Doing "AzureWebJobsStorage": "" will work. Starting Azurite Blob Service myself will work as well.
There are some inconsistencies between how different runtimes handle this:
Proposition: a way to attempt to start Azurite when debugging/starting func host before telling the user it's not installed. There is a VS Code command for that:
vscode.commands.executeCommand('azurite.start')
This way we can standardize how all runtimes handle this case - as not all triggers will not use Azurite as well
The text was updated successfully, but these errors were encountered: