Bump Microsoft.Azure.Functions.Worker and Microsoft.Azure.Functions.Worker.Extensions.Http.AspNetCore

[dependabot]

Bumps Microsoft.Azure.Functions.Worker and Microsoft.Azure.Functions.Worker.Extensions.Http.AspNetCore. These dependencies needed to be updated together.
Updates Microsoft.Azure.Functions.Worker from 2.0.0-preview2 to 2.0.0

Release notes

Sourced from Microsoft.Azure.Functions.Worker's releases.

Microsoft.Azure.Functions.Worker.ApplicationInsights 2.0.0

What's Changed

Microsoft.Azure.Functions.Worker.ApplicationInsights 2.0.0

• Updated Microsoft.Azure.Functions.Worker.Core dependency to 2.0.0

Microsoft.Azure.Functions.Worker.Extensions.Http.AspNetCore 2.0.0

What's Changed

Microsoft.Azure.Functions.Worker.Extensions.Http.AspNetCore 2.0.0

• Addressing fix for AspNetCoreResponseCookies cookie defaults (#2811)
• Support for IHostApplicationBuilder

Microsoft.Azure.Functions.Worker.Sdk 2.0.0

What's Changed

Microsoft.Azure.Functions.Worker.Sdk 2.0.0

• Updated Microsoft.Azure.Functions.Worker.Sdk.Generators reference to 1.3.4.
• Setting _ToolingSuffix for TargetFrameworkVersion v9.0
• Adding support for SDK container builds with Functions base images
• Support for dotnet run

Microsoft.Azure.Functions.Worker 2.0.0

Microsoft.Azure.Functions.Worker (metapackage) 2.0.0

• Updating Microsoft.Azure.Functions.Worker.Core to 2.0.0
• Updating Microsoft.Azure.Functions.Worker.Grpc to 2.0.0
• Changed exception handling in function invocation path to ensure fatal exceptions bubble up.

Breaking Changes

• Dropping .NET 5 TFM support
• Capability IncludeEmptyEntriesInMessagePayload is now enabled by default (#2701)
  • This means that empty entries will be included in the function trigger message payload by default.
  • To disable this capability and return to the old behaviour, set IncludeEmptyEntriesInMessagePayload to false in the worker options.
• ValidateScopes is enabled for development environments by default.

Microsoft.Azure.Functions.Worker.Core 2.0.0

• Updating Azure.Core to 1.41.0
• New APIs supporting IHostApplicationBuilder
• Updated service registrations for bootstrapping methods to ensure idempotency.

Breaking Changes

• Capability EnableUserCodeException is now enabled by default (#2702)
  • This means that exceptions thrown by user code will be surfaced to the Host as their original exception type, instead of being wrapped in an RpcException.

... (truncated)

Changelog

Sourced from Microsoft.Azure.Functions.Worker's changelog.

Microsoft.Azure.Functions.Worker (metapackage) 2.0.0

• Updating Microsoft.Azure.Functions.Worker.Core to 2.0.0
• Updating Microsoft.Azure.Functions.Worker.Grpc to 2.0.0

Microsoft.Azure.Functions.Worker.Core 2.0.0

• ValidateScopes is enabled for developement environments by default. (#2705)
  • The default is the value of IsDevelopment(IHostingEnvironment).
• Capability IncludeEmptyEntriesInMessagePayload is now enabled by default (#2701)
  • This means that empty entries will be included in the function trigger message payload by default.
  • To disable this capability and return to the old behaviour, set IncludeEmptyEntriesInMessagePayload to false in the worker options.
• Capability EnableUserCodeException is now enabled by default (#2702)
  • This means that exceptions thrown by user code will be surfaced to the Host as their original exception type, instead of being wrapped in an RpcException.
  • To disable this capability and return to the old behaviour, set EnableUserCodeException to false in the worker options.
  • The EnableUserCodeException property in WorkerOptions has been marked as obsolete and may be removed in a future release.
• Rename ILoggerExtensions to FunctionsLoggerExtensions to avoid naming conflict issues (#2716)
• Updating Azure.Core to 1.41.0
• Updated service registrations for bootstrapping methods to ensure idempotency.

Setting worker options example

var host = new HostBuilder()
.ConfigureFunctionsWorkerDefaults(options =>
{
    options.EnableUserCodeException = false;
    options.IncludeEmptyEntriesInMessagePayload = false;
})

Microsoft.Azure.Functions.Worker.Grpc 2.0.0

• Removed fallback command line argument reading code for grpc worker startup options. (#1908)

Commits

• See full diff in compare view

Updates Microsoft.Azure.Functions.Worker.Extensions.Http.AspNetCore from 2.0.0-preview2 to 2.0.0

Release notes

Sourced from Microsoft.Azure.Functions.Worker.Extensions.Http.AspNetCore's releases.

Microsoft.Azure.Functions.Worker.ApplicationInsights 2.0.0

What's Changed

Microsoft.Azure.Functions.Worker.ApplicationInsights 2.0.0

• Updated Microsoft.Azure.Functions.Worker.Core dependency to 2.0.0

Microsoft.Azure.Functions.Worker.Extensions.Http.AspNetCore 2.0.0

What's Changed

Microsoft.Azure.Functions.Worker.Extensions.Http.AspNetCore 2.0.0

• Addressing fix for AspNetCoreResponseCookies cookie defaults (#2811)
• Support for IHostApplicationBuilder

Microsoft.Azure.Functions.Worker.Sdk 2.0.0

What's Changed

Microsoft.Azure.Functions.Worker.Sdk 2.0.0

• Updated Microsoft.Azure.Functions.Worker.Sdk.Generators reference to 1.3.4.
• Setting _ToolingSuffix for TargetFrameworkVersion v9.0
• Adding support for SDK container builds with Functions base images
• Support for dotnet run

Microsoft.Azure.Functions.Worker 2.0.0

Microsoft.Azure.Functions.Worker (metapackage) 2.0.0

• Updating Microsoft.Azure.Functions.Worker.Core to 2.0.0
• Updating Microsoft.Azure.Functions.Worker.Grpc to 2.0.0
• Changed exception handling in function invocation path to ensure fatal exceptions bubble up.

Breaking Changes

• Dropping .NET 5 TFM support
• Capability IncludeEmptyEntriesInMessagePayload is now enabled by default (#2701)
  • This means that empty entries will be included in the function trigger message payload by default.
  • To disable this capability and return to the old behaviour, set IncludeEmptyEntriesInMessagePayload to false in the worker options.
• ValidateScopes is enabled for development environments by default.

Microsoft.Azure.Functions.Worker.Core 2.0.0

• Updating Azure.Core to 1.41.0
• New APIs supporting IHostApplicationBuilder
• Updated service registrations for bootstrapping methods to ensure idempotency.

Breaking Changes

• Capability EnableUserCodeException is now enabled by default (#2702)
  • This means that exceptions thrown by user code will be surfaced to the Host as their original exception type, instead of being wrapped in an RpcException.

... (truncated)

Changelog

Sourced from Microsoft.Azure.Functions.Worker.Extensions.Http.AspNetCore's changelog.

Microsoft.Azure.Functions.Worker (metapackage) 2.0.0

• Updating Microsoft.Azure.Functions.Worker.Core to 2.0.0
• Updating Microsoft.Azure.Functions.Worker.Grpc to 2.0.0

Microsoft.Azure.Functions.Worker.Core 2.0.0

• ValidateScopes is enabled for developement environments by default. (#2705)
  • The default is the value of IsDevelopment(IHostingEnvironment).
• Capability IncludeEmptyEntriesInMessagePayload is now enabled by default (#2701)
  • This means that empty entries will be included in the function trigger message payload by default.
  • To disable this capability and return to the old behaviour, set IncludeEmptyEntriesInMessagePayload to false in the worker options.
• Capability EnableUserCodeException is now enabled by default (#2702)
  • This means that exceptions thrown by user code will be surfaced to the Host as their original exception type, instead of being wrapped in an RpcException.
  • To disable this capability and return to the old behaviour, set EnableUserCodeException to false in the worker options.
  • The EnableUserCodeException property in WorkerOptions has been marked as obsolete and may be removed in a future release.
• Rename ILoggerExtensions to FunctionsLoggerExtensions to avoid naming conflict issues (#2716)
• Updating Azure.Core to 1.41.0
• Updated service registrations for bootstrapping methods to ensure idempotency.

Setting worker options example

var host = new HostBuilder()
.ConfigureFunctionsWorkerDefaults(options =>
{
    options.EnableUserCodeException = false;
    options.IncludeEmptyEntriesInMessagePayload = false;
})

Microsoft.Azure.Functions.Worker.Grpc 2.0.0

• Removed fallback command line argument reading code for grpc worker startup options. (#1908)

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[eerhardt]

LGTM

[eerhardt]

FYI - @bradygaster @DamianEdwards @captainsafia

[captainsafia]

Validated local and deployed end-to-end and azd up with these changes. LGTM!