How do I change the Environment Name in my Azure Functions project?

[AwkEng]

How can I change the Environment of my Azure Function project being hosted by Aspire?

My 'builder.Environment.EnvironmentName' property seems to be locked to 'Production' no matter what I do. I've tried modifying with launchSettings.json with ASPNETCORE_ENVIRONMENT, DOTNET_ENVIRONMENT, and even AZURE_FUNCTIONS_ENVIRONMENT environment variables. I've tried passing in '--environment' and '--launch-profile' arguments using WithArgs(). No luck.

I noticed the 'builder.AddAzureFunctionsProject() method does not allow passing in launch setting like other project resources, so that is not an option.

Am I out of luck?

[davidfowl]

Did you try setting AZURE_FUNCTIONS_ENVIRONMENT using WithEnvironment?

[AwkEng]

Yes, using WithEnvironment("AZURE_FUNCTIONS_ENVIRONMENT", "Testing") does change the "AZURE_FUNCTIONS_ENVIRONMENT" variable. However, EnvironmentName property on the builder stays as 'Production'.

I'm trying to use the EnvironmentName across multiple project resources to set specific connection strings during integrating testing. Its a bit cumbersome to have to check a separate configuration parameter just for the Azure Function project. My work around right now is to use my own environmental variable to track the running environment.

[davidfowl]

Are you trying to set the environment from your integration test to testing? You can use the API in creative ways to do this without affecting the apphost code directly.

[AwkEng]

Yes.

I know there are likely better solutions out there, but I'm having trouble finding examples that fit my scenario. I was just curious to what I could and could not do with the configuration in my functions project. I know its prerelease and should improve over time.

[mikanygTC]

I was unable to succeed in setting either of the 3 choices through launchSettings.json file for the function app. Seems like the Function integration doesn't load the launchSettings like AddProject() does.

But I manually set .WithEnvironment("DOTNET_ENVIRONMENT", "Development"); and confirmed it working with IHostEnvironment.IsDevelopment()

[Bouke]

Beware of Azure/azure-functions-dotnet-worker#2876 which makes the builder ignore AZURE_FUNCTIONS_ENVIRONMENT, and there's a fix for it Azure/azure-functions-dotnet-worker#2878 but it hasn't made it into a release yet.