Local.Setting.Json issues - ConnectionString #211
Comments
|
This seems to be a functions host problem, could you open an issue here https://github.com/Azure/azure-functions-host/issues ? |
|
I can do that certainly but have some doubts. When I do get the string from keyvault and the magic conversion happens from url to actual encoded connection string, it never binds correctly. That doesn't seem like a host issue but a binding problem because the string is correct at that point. Thx! |
Do you mean using a key vault URL instead of the actual connection string in the |
|
You might want to use identity-based connection instead: |
There's definitely some real flakiness when binding values from the local setting file. When using Azure functions input bindings it appears that keyVault or other complex objects (i.e. serilog setting) screws things up wherein the keyvault magic isn't performed or the AzureSignalRConnectionString doesn't bind to the function params. If other complex objects are in the values section, AzureSignalRConnectionString doesn't bind. Very frustrating.
{
"IsEncrypted": false,
"Values": {
},
"Serilog": {
"Using": [
"Serilog.Sinks.Console",
"Serilog.Sinks.File",
"Serilog.Sinks.AzureBlobStorage"
],
"MinimumLevel": {
"Default": "Information",
"Override": {
"Microsoft": "Warning",
"System": "Warning"
}
},
"WriteTo": [
{
"Name": "Console",
"Args": {
"writeInBatches": "true"
}
}
]
}
}
The text was updated successfully, but these errors were encountered: