Bump reactor-netty-http from 1.0.24 to 1.1.2 in /plugins/repository-azure

[dependabot]

Bumps reactor-netty-http from 1.0.24 to 1.1.2.

Release notes

Sourced from reactor-netty-http's releases.

v1.1.2

Reactor Netty 1.1.2 is part of 2022.0.2 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.2 by @​OlegDokuka in e5b22740efe8b1335b823d27398c2774c752e196, see release notes.
• Depend on Netty QUIC Codec v0.0.35.Final by @​violetagg in #2612
• Improve logging when connection closed after cancel by @​pderop in #2585
• Support configurable DNS resolver cache by @​samueldlightfoot in #2622

🐞 Bug fixes

• Ensure CL/TE headers are handled correctly for 204/205/304 status codes when server configured with HTTP/2 by @​violetagg in #2623
• Ensure HttpServer Active Connections metric is correct when connection closure before response write by @​violetagg in #2633

📖 Documentation, Tests and Build

• Documentation:
  • Update ReactorNetty#IO_SELECT_COUNT javadoc by @​violetagg in #2626
  • Fix typos in comments of HttpClientConnect by @​sgc109 in #2627
  • Update ReadMe to have consistent formatting by @​esivakumar18 in #2632
  • Add Reactor Netty version of Telnet example by @​jchenga in #2617
• Build:
  • Use new GitHub Actions API for setting output by @​violetagg in #2635

🆙 Dependency Upgrades

• Bump mockito-core to version 4.11.0 by @​dependabot in #2629
• Bump build-info-extractor-gradle to version 4.31.0 by @​dependabot in #2630
• Bump com.diffplug.spotless to version 6.12.1 by @​dependabot in #2631
• Bump assertj-core to version 3.24.1 by @​dependabot in #2637
• Bump netty-tcnative-boringssl-static to version 2.0.55.Final by @​violetagg in #2638

New Contributors

• @​sgc109 made their first contribution in #2627
• @​esivakumar18 made their first contribution in #2632
• @​jchenga made their first contribution in #2617

Full Changelog: reactor/reactor-netty@v1.1.1...v1.1.2

v1.1.1

Reactor Netty 1.1.1 is part of 2022.0.1 Release Train.

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

What's Changed

✨ New features and improvements

... (truncated)

Commits

• e5b2274 [release] Prepare and release 1.1.2
• ed8714d Merge-ignore release 1.0.27 into 1.1.2
• f781949 [release] Back to snapshots, next is 1.0.28-SNAPSHOT
• 018693b [release] Prepare and release 1.0.27
• 68c658d Merge #2638 into 1.1.2
• e05c0d7 Bump netty-tcnative-boringssl-static to version v2.0.55.Final (#2638)
• 05bc3c4 Merge #2637 into 1.1.2
• cba1a4c Bump assertj-core from 3.24.0 to 3.24.1 (#2637)
• 866f78f Merge #2635 into 1.1.2
• 823ae04 [chore] Use new GHA API for setting output (#2635)
• 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/9758/
• CommitID: e230c0f
  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: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/9759/
• CommitID: 83e6624
  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?

[kotwanikunal]

@dependabot recreate

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/9763/
• CommitID: 1c84af2
  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: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/9764/
• CommitID: 8bd5cd1
  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: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/9765/
• CommitID: e26f17b
  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: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/9825/
• CommitID: 683b1e3
  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: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/9828/
• CommitID: cd71915
  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: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/9829/
• CommitID: 944d8c6
  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: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/10185/
• CommitID: dc6577a
  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: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/10186/
• CommitID: 57d79f3
  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: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/10187/
• CommitID: 691dda4
  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: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/10893/
• CommitID: 789e692
  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: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/10903/
• CommitID: 789e692
  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?

[VachaShah]

Gradle Check (Jenkins) Run Completed with:

• RESULT: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/10903/
• CommitID: 789e692
  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?

Unrelated failure: #1715

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/10958/
• CommitID: 789e692
  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: UNSTABLE ❕
• TEST FAILURES:

      2 org.opensearch.extensions.ExtensionsManagerTests.classMethod
      1 org.opensearch.extensions.ExtensionsManagerTests.testInitialize

• URL: https://build.ci.opensearch.org/job/gradle-check/10969/
• CommitID: 597d9de
  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-5973-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 cef446c57d37b54c9c4e11f3ec87096d5935491b
# Push it to GitHub
git push --set-upstream origin backport/backport-5973-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-5973-to-2.x.