Open shibayan opened 3 years ago
This looks like it comes from:
Related changes had to be made to the Core Tools, although those could force the process to exit, while this seems to just be warning level. This should still be fixed. Core Tools PRs for reference in case it's useful in resolution:
Hello, this issue still happens on version 4.1.3
@mattchenderson still happening at 4.3.0 :(
Any guidance?
When using Managed Identity in Binding / Trigger, you need to specify a nested value prefixed with the connection name. (Example:
<CONNECTION_NAME_PREFIX>__serviceUri
)https://docs.microsoft.com/en-us/azure/azure-functions/functions-reference#connection-properties
Function Build SDK does not take nested values into account, so even if you add the correct settings to
local.settings.json
, it will warn you that the connection cannot be found, which is an unnecessary warning.Build warning
Repro code