azure-functions-node | A node.js client library for Azure Functions | Azure library

You can install the remote development extension tools for VSCode and the Azure Functions extension.

Create your local folder then using the remote development tools, open that folder inside a container from the command pallette by selecting 'Reopen In Container'

Reopen In Container Image

Then select your definition.

Remote Dev Tools Image

This actually use those base images you mentioned.

It will create a .devcontainer hidden directory in your repo where it stores the container information and saves you having to install the Function Core tools/NPM or anything else on your local machine.

It automatically forwards the required ports for local debugging and you can push the devcontainer definitions to source control so that others can use your definition with the project.

After writing up this whole big question, and proof reading it... I noticed this little snippet in the release task YAML (which I hadn't seen before today as it's a release and uses the AzDO GUI for editing):

runtimeStack: 'DOCKER|microsoft/azure-functions-node8:2.0'

It turns out, if you specify the stack as 'JavaScript' (the options are .NET and JavaScript) the task sets the "runtimeStack" to that string. Which is what gets set in the linuxFxVersion setting on the Function App. Even if you override that setting in the configuration settings.

The fix is to leave the Runtime field blank and then it will respect your settings. Awesome.

Let me paraphrase what you asked:

• You want just to retrieve blob storage object upon http request.

I think it is worth looking into bindings. They simplify the integration with other Azure services - Storage Accounts, Service Bus, Twilio - and Function Apps.

In your case it should be an input binding for blob storage. As one way to achieve it you need to customize your route in the http trigger part of function.json as follows: file/{fileName}. Then you use fileName in input binding definition in the same function.json.

I think function.json should like this:

It was an old tip used to remind us default storage connection AzureWebJobsStorage is not set correctly, which had been improved to be more intelligible long time ago. See this issue and its fix.

Looks like in docker image, this fix is omitted somehow.

To solve your problem, just set AzureWebJobsStorage in your Dockerfile.

Azure Functions is built on top of App Service, and ARM is indeed supported.

You can find links to the REST API and template format for Function Apps under the Web & Mobile section here