Bala G
Bala G
I have opened an internal workitem to start enforcing this limit when an attempt is made to add such a long env. variable from Portal or other clients. This should...
The docs should be updated soon. The limit has been set to 100 characters based on the telemetry. Adding an env. variable name with a length longer than that would...
Longterm we need a different solution for configuring nested configs via app settings. But we can increase the limit to 150 short term to improve things a bit.
Could you check if the correct slot name shows up in kudu https://{appname}.scm.azurewebsites.net/api/settings https://{appname}-staging.scm.azurewebsites.net/api/settings
We are still investigating this. But in the meantime could you restart the production slot and see if that fixes the issue?
@shubDhond This is the issue we were discussing last week. Please update here if you have any ideas.
Looks like the app is in consumption sku, so allow listing possibleOutboundIpAddresses alone is not sufficient. https://docs.microsoft.com/en-us/azure/azure-functions/ip-addresses#find-outbound-ip-addresses >When a function app that runs on the Consumption plan or the Premium...
I think there are 2 issues: Issue 1)There are possible code paths where host will consider itself to be fully specialized and return that status even if the specialization failed...
Yes, this issue is specific to consumption plans only.
@NvHeijningen @rodchenkov yes, this is still a limitation and we don't have an ETA yet. Are you able to workaround this in the meantime?