-
Notifications
You must be signed in to change notification settings - Fork 356
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Azure Function Isolated Mode. Microsoft.Azure.WebJobs.Host: Error indexing method 'Functions....'. Microsoft.Azure.WebJobs.Host: '%Azure:ServiceBus:Queue%' does not resolve to a value. #3070
Comments
The nameResolver parametr added
I can only get my function app to read %somevalue% in a queue trigger if it is set as an environment variable after switching to isolated mode. If it is set in appsettings.json its ignored and I get the same error as you get. It seems like whatever INameResolver is used in Note: In the application, if i inject IConfiguration anywhere, it has all values from appsettings.json. |
I was hunting this issue as well - after migration from net6 InProc to net8 Isolated, none of the Functions with timer trigger using the %% syntax started. It's a nasty regression, we have around 20 functions with reasonable defaults in appsettings.json. In TEST env we used to override it in AppService App Settings to execute more often so we don't have to wait during the testing but in higher environments we only override when troubleshooting.. So now just to get it up and running we need to pollute the AppService with all these settings.. |
Just ran into this issue as well. Have to say isolated functions lacks support for a LOT of seemingly basic features like this... |
I had the same issue after migration from .net 6 in-process to .net 8 isolated. I use also the timer trigger with the %% syntax and it wasn't working. I moved my cron settings in local.settings.json to "Values" section and it works as before. local.settings.json:
|
I am also having this exact issue - the isolated model is not really usable right now in a production environment. The docs look the same for a couple of months and the bug does not seem to be fixed at all, very sad :( |
I also had this issue. I created a workaround by creating a custom FunctionMetadataProvider and replacing the values in the RawBindings:
|
I'm curious if you had to register this class somehow so that it would be loaded/recognized. Apologies if this is obvious to most, but I'm not sure what to do with this class and would greatly appreciate your help! |
We are having the same issue in migrating a TimerTrigger from In-Process to Isolated.
We get the error: %MySchedule% does not resolve to a value.at Microsoft.Azure.WebJobs.Host.NameResolverExtensions.ResolveWholeStringCore(INameResolver resolver,String resolve,Boolean throwOnFailure) |
I use the CustomFunctionMetadata above but having this issue with the connection:
Amelsfort |
I am having the same issue. I am reading my setting from Azure app configuration. Any work around? |
Azure Function Isolated Mode.
Microsoft.Azure.WebJobs.Host: Error indexing method 'Functions....'. Microsoft.Azure.WebJobs.Host: '%KEY:NAME%' does not resolve to a value.
My configuration:
Usage:
"%Azure:ServiceBus:Queue%" and "SERVICEBUS:CONNECTION:STRING" are taking from an AzureKeyVault (HostBuilder config)
Error:
Microsoft.Azure.WebJobs.Host: Error indexing method 'Functions.Function-Name'. Microsoft.Azure.WebJobs.Host: '%Azure:ServiceBus:Queue%' does not resolve to a value.
My assumption:
The problem is in the FunctionIndexProvider.cs file.
The INameResolver does not passing (null instead) to the constructor.
The text was updated successfully, but these errors were encountered: