For local development I can get away doing Environment.GetEnvironmentVariable("ApiKey") and in my local.settings.json file I would have a JSON property ApiKey: "abc123".
But when I publish my function from Visual Studio or from Azure Pipeline into Staging or Production. They should be reading config values as per environment and some from KeyVault as well.
I have worked with Consul on-prem installation and it was a breeze. I am not sure what should be the right approach in case of Azure. Use Azure App Configuration service with labels for environments or go into each function instance and manually add configurations and map some with KeyVault?
