FUNCTIONS_WORKER_RUNTIME required in flex consumption app settings

[alecglen]

Version

Currently using 4.2.2

Description

Flex consumption plans have deprecated the FUNCTIONS_WORKER_RUNTIME app setting, and in fact it can't be added through normal means.

Despite that, Core Tools still requires the setting to be present in order to run locally, and automatically adds it to my local settings, de-syncing my local and hosted settings.

Steps to reproduce

Create a flex consumption app and run it.

[liliankasem]

The CLI does still require this information to run. Your local.settings.json should never be deployed to your production environment - can you expand more on how this is impacting you?

[alecglen]

@liliankasem it's not other than the warning. No problem if that's intended behavior, the inconsistent interface just caught me off guard. Could the CLI not infer the runtime same as the hosted app?

[liliankasem]

Unfortunately, FUNCTIONS_WORKER_RUNTIME is very ingrained in how this CLI was built so it's not so easy to move away from that at the moment, but there future plans to improve the CLI in general, including plans to remove local.settings.json which may also include removing the need for this environment variable to be set. This is currently lower priority as there are much bigger issues we need to address.

[Whadup]

Still broken in February :-(

az functionapp devops-pipeline create also requires the FUNCTIONS_WORKER_RUNTIME setting