The connection string to my queue (regardless of how many times I have generated a new one in the storage account) uses the symbol % in the connection string.
This is causing issues when I am trying to run the function locally using "func start". I receive errors that either the %xxxx% does not resolve to a value or % does not have a matching %.
This seems like a bug to me since I am able to connect to queue just fine with a Django server that is part of the same system.
More info from verbose output:
Microsoft.Azure.WebJobs.Host: Error indexing method 'Functions.xxxxxx'. Microsoft.Azure.WebJobs.Host: %xxx% does not resolve to a value.
The trigger is being written in python 3.11 and it seems that evaluating the string during connection isn't the issue but indexing the string is the issue but this is a string that is auto-generated by the Azure Storage security and networking UI.
Has anyone ran into this weird issue before? Any help would be appreciated. Thanks.
The connection string to my queue (regardless of how many times I have generated a new one in the storage account) uses the symbol % in the connection string.
This is causing issues when I am trying to run the function locally using "func start". I receive errors that either the %xxxx% does not resolve to a value or % does not have a matching %.
This seems like a bug to me since I am able to connect to queue just fine with a Django server that is part of the same system.
More info from verbose output:
Microsoft.Azure.WebJobs.Host: Error indexing method 'Functions.xxxxxx'. Microsoft.Azure.WebJobs.Host: %xxx% does not resolve to a value.
The trigger is being written in python 3.11 and it seems that evaluating the string during connection isn't the issue but indexing the string is the issue but this is a string that is auto-generated by the Azure Storage security and networking UI.
Has anyone ran into this weird issue before? Any help would be appreciated. Thanks.
Share Improve this question edited Feb 17 at 18:23 marc_s 755k184 gold badges1.4k silver badges1.5k bronze badges asked Feb 17 at 17:46 TheLiquorTheLiquor 717 bronze badges1 Answer
Reset to default 0I changed to the non signed version of the connection strings and placed them in local.settings.json instead of calling them directly in the function decorator argument. Seems to have resolved the issue.
No bug, just an uninformative error message.