Bump io.projectreactor.netty:reactor-netty-http from 1.1.7 to 1.1.8 in /plugins/repository-azure

[dependabot]

Bumps io.projectreactor.netty:reactor-netty-http from 1.1.7 to 1.1.8.

Release notes

Sourced from io.projectreactor.netty:reactor-netty-http's releases.

v1.1.8

Reactor Netty 1.1.8 is part of 2022.0.8 Release Train.

This is a recommended update for all Reactor Netty 1.1.x users.

What's Changed

✨ New features and improvements

• Depend on Reactor Core v3.5.7 by @​OlegDokuka in f81eef10da8b52c147f259b98027a2c1321f5e43, see release notes
• Depend on Netty v4.1.93.Final by @​violetagg in #2812
• Depend on Netty QUIC Codec v0.0.45.Final by @​violetagg in #2819
• HttpServer: Add API for specifying max streams per connection. The connection is marked for closing once the number of all-time streams reaches max streams configuration by @​violetagg in #2817

🐞 Bug fixes

• Ensure any custom CL/TE header is removed when 304 response code by @​violetagg in #2820

📖 Documentation, Tests and Build

• Add Brotli compression test by @​sullis in #2815
• Add test for IllegalReferenceCountException/sendObject by @​pderop in #2821

🆙 Build/Test Dependency Upgrades

• Bump netty-tcnative-boringssl-static to version v2.0.61.Final by @​violetagg in #2799
• Bump braveVersion to version 5.16.0 by @​dependabot in #2801
• Bump build-info-extractor-gradle to version 4.32.0 by @​dependabot in #2807
• Bump org.gradle.test-retry to version 1.5.3 by @​dependabot in #2810
• Bump jackson-databind to version 2.15.2 by @​dependabot in #2816
• Bump tomcat-embed-core to version 9.0.76 by @​dependabot in #2830

New Contributors

• @​sullis made their first contribution in #2815

Full Changelog: reactor/reactor-netty@v1.1.7...v1.1.8

Commits

• f81eef1 [release] Prepare and release 1.1.8
• e00d347 Merge-ignore release 1.0.33 into 1.1.8
• 3be4c34 [release] Back to snapshots, next is 1.0.34-SNAPSHOT
• d3fb8ec [release] Prepare and release 1.0.33
• 2b0e29a Merge #2830 into 1.1.8
• 01dded0 Bump org.apache.tomcat.embed:tomcat-embed-core from 9.0.75 to 9.0.76 (#2830)
• 253e767 Merge #2821 into 1.1.8
• c71390e Add test for IllegalReferenceCountException/sendObject (#2821)
• 7fef5e7 Merge #2820 into 1.1.8
• 32459b2 Ensure any custom CL/TE header is removed when 304 response code (#2820)
• Additional commits viewable 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 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)

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/18343/
• CommitID: 0533e09
  Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green.
  Is the failure a flaky test unrelated to your change?

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: SUCCESS ✅
• URL: https://build.ci.opensearch.org/job/gradle-check/18344/
• CommitID: 0f32d50

[codecov]

Codecov Report

Merging #8256 (d97f39d) into main (9aad3a3) will increase coverage by 0.02%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##               main    #8256      +/-   ##
============================================
+ Coverage     70.89%   70.92%   +0.02%     
- Complexity    56705    56723      +18     
============================================
  Files          4733     4733              
  Lines        268129   268129              
  Branches      39285    39285              
============================================
+ Hits         190090   190165      +75     
+ Misses        62070    61933     -137     
- Partials      15969    16031      +62     

see 433 files with indirect coverage changes

[reta]

@dependabot recreate please

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/18357/
• CommitID: 4dd7001
  Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green.
  Is the failure a flaky test unrelated to your change?

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: SUCCESS ✅
• URL: https://build.ci.opensearch.org/job/gradle-check/18359/
• CommitID: 29e17fd

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: UNSTABLE ❕
• TEST FAILURES:

      1 org.opensearch.action.admin.cluster.node.tasks.ResourceAwareTasksTests.testBasicTaskResourceTracking

• URL: https://build.ci.opensearch.org/job/gradle-check/18360/
• CommitID: d97f39d
  Please review all flaky tests that succeeded after retry and create an issue if one does not already exist to track the flaky failure.

[opensearch-trigger-bot]

The backport to 2.x failed:

The process '/usr/bin/git' failed with exit code 128

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/backport-2.x 2.x
# Navigate to the new working tree
pushd ../.worktrees/backport-2.x
# Create a new branch
git switch --create backport/backport-8256-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 c29e4aa774199b007acffd17bb016f4bfc681874
# Push it to GitHub
git push --set-upstream origin backport/backport-8256-to-2.x
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/backport-2.x

Then, create a pull request where the base branch is 2.x and the compare/head branch is backport/backport-8256-to-2.x.