Azure / Azure/azure-functions-host
Log additional information when unresolved bindings are found
- Dominant language
- C#
- Stars
- 2k
- Forks
- 482
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 36
Description
Currently, the `VerifyResolvedBindings` throws an error such as below when there are unresolved bindings.
> The '{FunctionName}' function is in error: The binding type(s) '{TriggerName}' were not found in the configured extension bundle. Please ensure the type is correct and the correct version of extension bundle is configured.
We should log more information (the metadata and inputbindings used) which will help us understand what specifically caused the error, so that a valud .
https://github.com/Azure/azure-functions-host/blob/eb76715a57649d269232d1375a7a2c23ee73dd0a/src/WebJobs.Script/Description/FunctionDescriptorProvider.cs#L78-L86
A recent CRI where this behavior was spotted: 474324655.
The issue was transient after a deployment. Manual restart of the app fixed the issue
Contributor guide
Research direction
Start in src/WebJobs.Script/Description/FunctionDescriptorProvider.cs at VerifyResolvedBindings, as linked in the issue. Review how unresolved bindings are detected and determine how the metadata and inputbindings should be included in logs. Done means the unresolved-binding error provides the additional information needed to understand the failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, csharp
- Domain
- backend, observability
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100