Skip to content

Remove typo from ML cluster settings#3529

Merged
Naarcha-AWS merged 2 commits intomainfrom
Naarcha-AWS-cluster-settings-update
Mar 20, 2023
Merged

Remove typo from ML cluster settings#3529
Naarcha-AWS merged 2 commits intomainfrom
Naarcha-AWS-cluster-settings-update

Conversation

@Naarcha-AWS
Copy link
Contributor

@Naarcha-AWS Naarcha-AWS commented Mar 20, 2023

Also fixes default value of sync up jobs.

Checklist

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

@Naarcha-AWS Naarcha-AWS requested a review from a team as a code owner March 20, 2023 19:47
@Naarcha-AWS Naarcha-AWS added backport 2.0 PR: Backport label for v2.0.x backport 2.1 PR: Backport label for 2.1 backport 2.2 PR: Backport label for 2.2 backport 2.3 PR: Backport label for 2.3 backport 2.4 PR: Backport label for 2.4 backport 2.5 PR: Backport label for 2.5 backport 2.6 PR: Backport label for 2.6 labels Mar 20, 2023
Change default value
@Naarcha-AWS Naarcha-AWS merged commit 32bc0d2 into main Mar 20, 2023
@opensearch-trigger-bot
Copy link
Contributor

The backport to 2.0 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.0 2.0
# Navigate to the new working tree
pushd ../.worktrees/backport-2.0
# Create a new branch
git switch --create backport/backport-3529-to-2.0
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 32bc0d236e09a06b268da6fcdbd80feefe3fcad8
# Push it to GitHub
git push --set-upstream origin backport/backport-3529-to-2.0
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/backport-2.0

Then, create a pull request where the base branch is 2.0 and the compare/head branch is backport/backport-3529-to-2.0.

@opensearch-trigger-bot
Copy link
Contributor

The backport to 2.1 failed:

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

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.1 2.1
# Navigate to the new working tree
pushd ../.worktrees/backport-2.1
# Create a new branch
git switch --create backport/backport-3529-to-2.1
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 32bc0d236e09a06b268da6fcdbd80feefe3fcad8
# Push it to GitHub
git push --set-upstream origin backport/backport-3529-to-2.1
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/backport-2.1

Then, create a pull request where the base branch is 2.1 and the compare/head branch is backport/backport-3529-to-2.1.

@opensearch-trigger-bot
Copy link
Contributor

The backport to 2.2 failed:

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

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.2 2.2
# Navigate to the new working tree
pushd ../.worktrees/backport-2.2
# Create a new branch
git switch --create backport/backport-3529-to-2.2
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 32bc0d236e09a06b268da6fcdbd80feefe3fcad8
# Push it to GitHub
git push --set-upstream origin backport/backport-3529-to-2.2
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/backport-2.2

Then, create a pull request where the base branch is 2.2 and the compare/head branch is backport/backport-3529-to-2.2.

@opensearch-trigger-bot
Copy link
Contributor

The backport to 2.3 failed:

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

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.3 2.3
# Navigate to the new working tree
pushd ../.worktrees/backport-2.3
# Create a new branch
git switch --create backport/backport-3529-to-2.3
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 32bc0d236e09a06b268da6fcdbd80feefe3fcad8
# Push it to GitHub
git push --set-upstream origin backport/backport-3529-to-2.3
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/backport-2.3

Then, create a pull request where the base branch is 2.3 and the compare/head branch is backport/backport-3529-to-2.3.

@opensearch-trigger-bot
Copy link
Contributor

The backport to 2.4 failed:

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

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.4 2.4
# Navigate to the new working tree
pushd ../.worktrees/backport-2.4
# Create a new branch
git switch --create backport/backport-3529-to-2.4
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 32bc0d236e09a06b268da6fcdbd80feefe3fcad8
# Push it to GitHub
git push --set-upstream origin backport/backport-3529-to-2.4
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/backport-2.4

Then, create a pull request where the base branch is 2.4 and the compare/head branch is backport/backport-3529-to-2.4.

@opensearch-trigger-bot
Copy link
Contributor

The backport to 2.5 failed:

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

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.5 2.5
# Navigate to the new working tree
pushd ../.worktrees/backport-2.5
# Create a new branch
git switch --create backport/backport-3529-to-2.5
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 32bc0d236e09a06b268da6fcdbd80feefe3fcad8
# Push it to GitHub
git push --set-upstream origin backport/backport-3529-to-2.5
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/backport-2.5

Then, create a pull request where the base branch is 2.5 and the compare/head branch is backport/backport-3529-to-2.5.

@opensearch-trigger-bot
Copy link
Contributor

The backport to 2.6 failed:

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

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.6 2.6
# Navigate to the new working tree
pushd ../.worktrees/backport-2.6
# Create a new branch
git switch --create backport/backport-3529-to-2.6
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 32bc0d236e09a06b268da6fcdbd80feefe3fcad8
# Push it to GitHub
git push --set-upstream origin backport/backport-3529-to-2.6
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/backport-2.6

Then, create a pull request where the base branch is 2.6 and the compare/head branch is backport/backport-3529-to-2.6.

Naarcha-AWS added a commit that referenced this pull request Mar 20, 2023
* Remove typo from ML cluster settings

* Update cluster-settings.md

Change default value

(cherry picked from commit 32bc0d2)
Naarcha-AWS added a commit that referenced this pull request Mar 20, 2023
* Remove typo from ML cluster settings

* Update cluster-settings.md

Change default value

(cherry picked from commit 32bc0d2)
Naarcha-AWS added a commit that referenced this pull request Mar 20, 2023
* Remove typo from ML cluster settings

* Update cluster-settings.md

Change default value

(cherry picked from commit 32bc0d2)
Naarcha-AWS added a commit that referenced this pull request Mar 20, 2023
* Remove typo from ML cluster settings

* Update cluster-settings.md

Change default value

(cherry picked from commit 32bc0d2)
Naarcha-AWS added a commit that referenced this pull request Mar 20, 2023
* Remove typo from ML cluster settings

* Update cluster-settings.md

Change default value

(cherry picked from commit 32bc0d2)
Naarcha-AWS added a commit that referenced this pull request Mar 20, 2023
* Remove typo from ML cluster settings

* Update cluster-settings.md

Change default value

(cherry picked from commit 32bc0d2)
vagimeli pushed a commit that referenced this pull request May 4, 2023
* Remove typo from ML cluster settings

* Update cluster-settings.md

Change default value
vagimeli added a commit that referenced this pull request May 4, 2023
harshavamsi pushed a commit to harshavamsi/documentation-website that referenced this pull request Oct 31, 2023
* Remove typo from ML cluster settings

* Update cluster-settings.md

Change default value
@Naarcha-AWS Naarcha-AWS deleted the Naarcha-AWS-cluster-settings-update branch March 28, 2024 23:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport 2.0 PR: Backport label for v2.0.x backport 2.1 PR: Backport label for 2.1 backport 2.2 PR: Backport label for 2.2 backport 2.3 PR: Backport label for 2.3 backport 2.4 PR: Backport label for 2.4 backport 2.5 PR: Backport label for 2.5 backport 2.6 PR: Backport label for 2.6

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants