You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the host is reading metadata via a custom metadata provider (code), we do not validate the metadata like we do in our other code path (i.e. the worker metadata provider).
Without the validation, function names can have unwanted characters such as / which can lead to further failures down the line i.e. with function keys, storage etc.
Updating the custom provider code path to validate the metadata would be a breaking change. To analyze if this should be a hard failure or if we should make any further changes here, we should add telemetry to this code path to give us a good idea of how many Function Apps would be impacted if we made changes here.
The text was updated successfully, but these errors were encountered:
Related to: Azure/azure-functions-dotnet-worker#788
When the host is reading metadata via a custom metadata provider (code), we do not validate the metadata like we do in our other code path (i.e. the worker metadata provider).
Without the validation, function names can have unwanted characters such as
/
which can lead to further failures down the line i.e. with function keys, storage etc.Updating the custom provider code path to validate the metadata would be a breaking change. To analyze if this should be a hard failure or if we should make any further changes here, we should add telemetry to this code path to give us a good idea of how many Function Apps would be impacted if we made changes here.
The text was updated successfully, but these errors were encountered: