Added the addition of the server version and distribution as a respon…

[Sam-ScottLogic]

…se header

Description

In this PR code has been added to the default rest channel file that adds a new custom header containing the server version.

Related Issues

Issue - (#6583)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/17686/
• CommitID: 2160b37
  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/17687/
• CommitID: db29578
  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/17755/
• CommitID: 3da7ec7
  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:

      1 org.opensearch.remotestore.RemoteStoreIT.testStaleCommitDeletionWithInvokeFlush

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

[github-actions]

Gradle Check (Jenkins) Run Completed with:

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

[Sam-ScottLogic]

Im not too sure why gradle is failing, tried to run ./gradlew :server:spotlessApply but no changes are applied

[github-actions]

Gradle Check (Jenkins) Run Completed with:

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

[reta]

Im not too sure why gradle is failing, tried to run ./gradlew :server:spotlessApply but no changes are applied

Flaky tests ... :( @Sam-ScottLogic could you please rebase against main? thank you

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: UNSTABLE ❕
• TEST FAILURES:

      1 org.opensearch.remotestore.RemoteStoreIT.testStaleCommitDeletionWithInvokeFlush

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

[Sam-ScottLogic]

Im not too sure why gradle is failing, tried to run ./gradlew :server:spotlessApply but no changes are applied

Flaky tests ... :( @Sam-ScottLogic could you please rebase against main? thank you

Merged main believe its fixed it

[reta]

@andrross looks good to you?

[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-8084-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 68ddf2442c57672ff65c72f39c36e66dcd2e4dd7
# Push it to GitHub
git push --set-upstream origin backport/backport-8084-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-8084-to-2.x.

[reta]

@Sam-ScottLogic could toy please send manual backport to 2.x branch? thank you

[Sam-ScottLogic]

@Sam-ScottLogic could toy please send manual backport to 2.x branch? thank you

Sorry for late response. Does this still need to be backported?

[dblock]

@Sam-ScottLogic I believe yes, if you want this in 2.x

[Sam-ScottLogic]

I dont mind it going in the next release just dont want to mess up what I've done messing up the series of git commands :)

[dblock]

Up to you to backport it.