The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

Non-nullable property 'api' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.

Non-nullable property 'requestId' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.

Non-nullable property 'eTag' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.

Non-nullable property 'contentType' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.

Non-nullable property 'blobType' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.

Non-nullable property 'url' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.

Non-nullable property 'sequencer' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.

Non-nullable property 'storageDiagnostics' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.

Non-nullable property 'batchId' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.

The registration for method 'ConfigureFunctionsWebApplication' is expected for ASP.NET Core Integration. (https://aka.ms/azfw-rules?ruleid=AZFW0014)

For improved performance, use the LoggerMessage delegates instead of calling 'LoggerExtensions.LogWarning(ILogger, string?, params object?[])' (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1848)

The logging message template should not vary between calls to 'LoggerExtensions.LogWarning(ILogger, string?, params object?[])' (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca2254)

For improved performance, use the LoggerMessage delegates instead of calling 'LoggerExtensions.LogWarning(ILogger, string?, params object?[])' (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1848)

The logging message template should not vary between calls to 'LoggerExtensions.LogWarning(ILogger, string?, params object?[])' (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca2254)

For improved performance, use the LoggerMessage delegates instead of calling 'LoggerExtensions.LogWarning(ILogger, string?, params object?[])' (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1848)

The logging message template should not vary between calls to 'LoggerExtensions.LogWarning(ILogger, string?, params object?[])' (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca2254)

For improved performance, use the LoggerMessage delegates instead of calling 'LoggerExtensions.LogWarning(ILogger, string?, params object?[])' (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1848)

The logging message template should not vary between calls to 'LoggerExtensions.LogWarning(ILogger, string?, params object?[])' (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca2254)

Change type of field 'fileInputs' from 'System.Collections.Generic.IList<string>' to 'System.Collections.Generic.List<string>' for improved performance (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1859)