Cannot enforce `development` enviromnet. Always defaults to `production`

[kepikoi]

The behavior described in https://github.com/MicrosoftDocs/azure-docs/issues/36045#issuecomment-516278405 is currently not reflected

Starting a node.js project always defaults to Production environment. Setting AZURE_FUNCTIONS_ENVIRONMENT via local.settings.json yields An item with the same key has already been added. Key: AZURE_FUNCTIONS_ENVIRONMENT. Right now I can't see how to start the core tools in development env.

Please honor NODE_ENV=development in local.settings.json or at least allow setting AZURE_FUNCTIONS_ENVIRONMENT manually

[ahmelsayed]

the core-tools always forces development for AZURE_FUNCTIONS_ENVIRONMENT (here)

You should be able to set NODE_ENV in local.settings.json

[mmulhearn]

I'm finding that when running locally in VS 2019, functions runs as "Production", which is the opposite of what documentation says. When I try to set "AZURE_FUNCTIONS_ENVIRONMENT": "Development", I get the error An item with the same key has already been added. Key: AZURE_FUNCTIONS_ENVIRONMENT. Setting NODE_ENV seems to do nothing.

Setup:
Azure Functions Core Tools (3.0.2106 Commit hash: 5431fca)
Function Runtime Version: 3.0.13107
.NET Core 3.1

[kepikoi]

the core-tools always forces development for AZURE_FUNCTIONS_ENVIRONMENT (here)

You should be able to set NODE_ENV in local.settings.json

Version 2.7.2184 doesn't! Always starts with Hosting environment: Production despite AZURE_FUNCTIONS_ENVIRONMENT=Development and NODE_ENV=development.

PS C:\www> func -V
2.7.2184
PS C:\www> node -v
v12.14.1
PS C:\www> npm -v
6.13.4
PS C:\www> [System.Environment]::OSVersion.Version

Major  Minor  Build  Revision
-----  -----  -----  --------
10     0      18362  0

[ahmelsayed]

There are many different environments here.

Functions Runtime: This is configured using AZURE_FUNCTIONS_ENVIRONMENT. This is always development in the core tools.
Node Environment: This is configured using NODE_ENV . The core tools doesn't have a default for this. You can set it in your shell or local.settings.json
ASP.NET Core Environment: This is configured using ASPNETCORE_ENVIRONMENT. You can specify that in your shell or local.settings.json. ASP.NET Core is what functions is built on. This is what correspond to Hosting environment: Production in the output.

[kepikoi]

@ahmelsayed thank you for clarifying the different scopes but what I'm asking is that that azure-function-core-tools is not behaving like documented

Functions Runtime: This is configured using AZURE_FUNCTIONS_ENVIRONMENT. This is always development in the core tools.

This is not the case in 2.7.2184. Here is a simple repro:

PS C:\www\.testing> mkdir func-prod-repro


    Verzeichnis: C:\www\.testing


Mode                LastWriteTime         Length Name
----                -------------         ------ ----
d-----       19.02.2020     09:16                func-prod-repro
PS C:\www\.testing> cd .\func-prod-repro\
PS C:\www\.testing\func-prod-repro> func init
Use the up/down arrow keys to select a worker runtime:node
Use the up/down arrow keys to select a language:javascript
Writing package.json
Writing .gitignore
Writing host.json
Writing local.settings.json
Writing C:\www\.testing\func-prod-repro\.vscode\extensions.json
PS C:\www\.testing\func-prod-repro> func new
Use the up/down arrow keys to select a template:HTTP trigger
Function name: [HttpTrigger] hello
Writing C:\www\.testing\func-prod-repro\hello\index.js
Writing C:\www\.testing\func-prod-repro\hello\function.json
The function "hello" was created successfully from the "HTTP trigger" template.
PS C:\www\.testing\func-prod-repro> func start

                  %%%%%%
                 %%%%%%
            @   %%%%%%    @
          @@   %%%%%%      @@
       @@@    %%%%%%%%%%%    @@@
     @@      %%%%%%%%%%        @@
       @@         %%%%       @@
         @@      %%%       @@
           @@    %%      @@
                %%
                %

Azure Functions Core Tools (2.7.2184 Commit hash: 5afacc827c2848e4debc23bb96604f1ffce09cc7)
Function Runtime Version: 2.0.12961.0
[19.02.2020 08:19:31] FUNCTIONS_WORKER_RUNTIME set to node. Skipping WorkerConfig for language:java
[19.02.2020 08:19:31] FUNCTIONS_WORKER_RUNTIME set to node. Skipping WorkerConfig for language:powershell
[19.02.2020 08:19:31] FUNCTIONS_WORKER_RUNTIME set to node. Skipping WorkerConfig for language:python
[19.02.2020 08:19:31] Building host: startup suppressed: 'False', configuration suppressed: 'False', startup operation id: '1e74edbe-fc91-407b-a36f-c2f1c6d9cf41'
[19.02.2020 08:19:31] Reading host configuration file 'C:\www\.testing\func-prod-repro\host.json'
[19.02.2020 08:19:31] Host configuration file read:
[19.02.2020 08:19:31] {
[19.02.2020 08:19:31]   "version": "2.0",
[19.02.2020 08:19:31]   "extensionBundle": {
[19.02.2020 08:19:31]     "id": "Microsoft.Azure.Functions.ExtensionBundle",
[19.02.2020 08:19:31]     "version": "[1.*, 2.0.0)"
[19.02.2020 08:19:31]   }
[19.02.2020 08:19:31] }
[19.02.2020 08:19:31] Reading functions metadata
[19.02.2020 08:19:31] 1 functions found
[19.02.2020 08:19:31] Looking for extension bundle Microsoft.Azure.Functions.ExtensionBundle at C:\Users\AlexeyUtin\AppData\Local\Temp\Functions\ExtensionBundles\Microsoft.Azure.Functions.ExtensionBundle
[19.02.2020 08:19:31] Found a matching extension bundle at C:\Users\AlexeyUtin\AppData\Local\Temp\Functions\ExtensionBundles\Microsoft.Azure.Functions.ExtensionBundle\1.1.1
[19.02.2020 08:19:31] Fetching information on versions of extension bundle Microsoft.Azure.Functions.ExtensionBundle available on https://functionscdn.azureedge.net/public/ExtensionBundles/Microsoft.Azure.Functions.ExtensionBundle/index.json
[19.02.2020 08:19:32] Skipping bundle download since it already exists at path C:\Users\AlexeyUtin\AppData\Local\Temp\Functions\ExtensionBundles\Microsoft.Azure.Functions.ExtensionBundle\1.1.1
[19.02.2020 08:19:32] Loading Extention bundle from C:\Users\AlexeyUtin\AppData\Local\Temp\Functions\ExtensionBundles\Microsoft.Azure.Functions.ExtensionBundle\1.1.1
[19.02.2020 08:19:32] Initializing Warmup Extension.
[19.02.2020 08:19:32] FUNCTIONS_WORKER_RUNTIME set to node. Skipping WorkerConfig for language:java
[19.02.2020 08:19:32] FUNCTIONS_WORKER_RUNTIME set to node. Skipping WorkerConfig for language:powershell
[19.02.2020 08:19:32] FUNCTIONS_WORKER_RUNTIME set to node. Skipping WorkerConfig for language:python
[19.02.2020 08:19:32] Initializing Host. OperationId: '1e74edbe-fc91-407b-a36f-c2f1c6d9cf41'.
[19.02.2020 08:19:32] Host initialization: ConsecutiveErrors=0, StartupCount=1, OperationId=1e74edbe-fc91-407b-a36f-c2f1c6d9cf41
[19.02.2020 08:19:32] LoggerFilterOptions
[19.02.2020 08:19:32] {
[19.02.2020 08:19:32]   "MinLevel": "None",
[19.02.2020 08:19:32]   "Rules": [
[19.02.2020 08:19:32]     {
[19.02.2020 08:19:32]       "ProviderName": null,
[19.02.2020 08:19:32]       "CategoryName": null,
[19.02.2020 08:19:32]       "LogLevel": null,
[19.02.2020 08:19:32]       "Filter": "<AddFilter>b__0"
[19.02.2020 08:19:32]     },
[19.02.2020 08:19:32]     {
[19.02.2020 08:19:32]       "ProviderName": "Microsoft.Azure.WebJobs.Script.WebHost.Diagnostics.SystemLoggerProvider",
[19.02.2020 08:19:32]       "CategoryName": null,
[19.02.2020 08:19:32]       "LogLevel": "None",
[19.02.2020 08:19:32]       "Filter": null
[19.02.2020 08:19:32]     },
[19.02.2020 08:19:32]     {
[19.02.2020 08:19:32]       "ProviderName": "Microsoft.Azure.WebJobs.Script.WebHost.Diagnostics.SystemLoggerProvider",
[19.02.2020 08:19:32]       "CategoryName": null,
[19.02.2020 08:19:32]       "LogLevel": null,
[19.02.2020 08:19:32]       "Filter": "<AddFilter>b__0"
[19.02.2020 08:19:32]     }
[19.02.2020 08:19:32]   ]
[19.02.2020 08:19:32] }
[19.02.2020 08:19:32] FunctionResultAggregatorOptions
[19.02.2020 08:19:32] {
[19.02.2020 08:19:32]   "BatchSize": 1000,
[19.02.2020 08:19:32]   "FlushTimeout": "00:00:30",
[19.02.2020 08:19:32]   "IsEnabled": true
[19.02.2020 08:19:32] }
[19.02.2020 08:19:32] SingletonOptions
[19.02.2020 08:19:32] {
[19.02.2020 08:19:32]   "LockPeriod": "00:00:15",
[19.02.2020 08:19:32]   "ListenerLockPeriod": "00:00:15",
[19.02.2020 08:19:32]   "LockAcquisitionTimeout": "10675199.02:48:05.4775807",
[19.02.2020 08:19:32]   "LockAcquisitionPollingInterval": "00:00:05",
[19.02.2020 08:19:32]   "ListenerLockRecoveryPollingInterval": "00:01:00"
[19.02.2020 08:19:32] }
[19.02.2020 08:19:32] HttpOptions
[19.02.2020 08:19:32] {
[19.02.2020 08:19:32]   "DynamicThrottlesEnabled": false,
[19.02.2020 08:19:32]   "MaxConcurrentRequests": -1,
[19.02.2020 08:19:32]   "MaxOutstandingRequests": -1,
[19.02.2020 08:19:32]   "RoutePrefix": "api"
[19.02.2020 08:19:32] }
[19.02.2020 08:19:32] Starting JobHost
[19.02.2020 08:19:32] Starting Host (HostId=winsegue-782203814, InstanceId=49f23b44-9a3f-41a7-a160-58dbfcf17547, Version=2.0.12961.0, ProcessId=11564, AppDomainId=1, InDebugMode=False, InDiagnosticMode=False, FunctionsExtensionVersion=(null))
[19.02.2020 08:19:32] Loading functions metadata
[19.02.2020 08:19:32] 1 functions loaded
[19.02.2020 08:19:32] Starting worker process:node  "C:\Users\AlexeyUtin\AppData\Roaming\nvm\v12.16.0\node_modules\azure-functions-core-tools\bin\workers\node\dist/src/nodejsWorker.js" --host 127.0.0.1 --port 61809 --workerId 2cf9d2a9-096f-458b-813f-e276efa4abe2 --requestId e9151309-53b6-4b51-bec0-048606c12d9d --grpcMaxMessageLength 134217728
[19.02.2020 08:19:32] node process with Id=22620 started
[19.02.2020 08:19:32] Generating 1 job function(s)
[19.02.2020 08:19:32] [warn] The Node.js version you are using (v12.16.0) is not fully supported by Azure Functions V2. We recommend using one the following major versions: 8, 10.
[19.02.2020 08:19:32] Found the following functions:
[19.02.2020 08:19:32] Host.Functions.hello
[19.02.2020 08:19:32]
[19.02.2020 08:19:32] Initializing function HTTP routes
[19.02.2020 08:19:32] Mapped function route 'api/hello' [get,post] to 'hello'
[19.02.2020 08:19:32]
[19.02.2020 08:19:32] Host initialized (243ms)
[19.02.2020 08:19:32] Host started (249ms)
[19.02.2020 08:19:33] Job host started
Hosting environment: Production
Content root path: C:\www\.testing\func-prod-repro
Now listening on: http://0.0.0.0:7071
Application started. Press Ctrl+C to shut down.

Http Functions:

        hello: [GET,POST] http://localhost:7071/api/hello

[19.02.2020 08:19:33] Worker 2cf9d2a9-096f-458b-813f-e276efa4abe2 connecting on 127.0.0.1:61809

As you can see a freshly bootstraped node runtime function is starting with Hosting environment: Production and not development

[ahmelsayed]

That's because that log message is about ASP.NET environment, not Functions Runtime environment. Functions Runtime is indeed in development mode above. ASP.NET isn't. Those are the default ASP.NET logs.

I'm not sure if the ASP.NET environment (production vs development) has any particular implications for functions. https://github.com/Azure/azure-functions-host would be the place to ask about that.