Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rework Clients, Tools, and Data Prepper section #1794

Merged
merged 3 commits into from
Nov 7, 2022
Merged

Conversation

Naarcha-AWS
Copy link
Collaborator

@Naarcha-AWS Naarcha-AWS commented Nov 2, 2022

Signed-off-by: Naarcha-AWS [email protected]

Closes part of #1036

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 added backport 2.0 PR: Backport label for v2.0.x 4 - Doc review PR: Doc review in progress 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 labels Nov 2, 2022
@Naarcha-AWS Naarcha-AWS requested a review from a team as a code owner November 2, 2022 18:25
Copy link
Collaborator

@kolchfa-aws kolchfa-aws left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@hdhalter
Copy link
Contributor

hdhalter commented Nov 2, 2022

@kolchfa-aws - Did you want to change the order of the list of clients? Python, .NET, Ruby, etc.? Or should we alphabetize them?

@kolchfa-aws
Copy link
Collaborator

We would like to revisit this order and just list languages. I will reorganize these pages after the 2.4 release.

@hdhalter
Copy link
Contributor

hdhalter commented Nov 3, 2022

OK, then we just need to move Grafana to Tools. Thanks!

@Naarcha-AWS Naarcha-AWS merged commit 4d6a275 into main Nov 7, 2022
@Naarcha-AWS Naarcha-AWS deleted the clients-toc branch November 7, 2022 18:41
@opensearch-trigger-bot
Copy link
Contributor

The backport to 2.0 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.0 2.0
# Navigate to the new working tree
cd .worktrees/backport-2.0
# Create a new branch
git switch --create backport/backport-1794-to-2.0
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 4d6a2759508d3b7e318e353281676cabb9bb8f9e
# Push it to GitHub
git push --set-upstream origin backport/backport-1794-to-2.0
# Go back to the original working tree
cd ../..
# 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-1794-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
cd .worktrees/backport-2.1
# Create a new branch
git switch --create backport/backport-1794-to-2.1
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 4d6a2759508d3b7e318e353281676cabb9bb8f9e
# Push it to GitHub
git push --set-upstream origin backport/backport-1794-to-2.1
# Go back to the original working tree
cd ../..
# 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-1794-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
cd .worktrees/backport-2.2
# Create a new branch
git switch --create backport/backport-1794-to-2.2
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 4d6a2759508d3b7e318e353281676cabb9bb8f9e
# Push it to GitHub
git push --set-upstream origin backport/backport-1794-to-2.2
# Go back to the original working tree
cd ../..
# 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-1794-to-2.2.

opensearch-trigger-bot bot pushed a commit that referenced this pull request Nov 7, 2022
* Rework Clients, Tools, and Data Prepper section

Signed-off-by: Naarcha-AWS <[email protected]>

* Add new Data Prepper files

Signed-off-by: Naarcha-AWS <[email protected]>

Signed-off-by: Naarcha-AWS <[email protected]>
(cherry picked from commit 4d6a275)
Naarcha-AWS added a commit that referenced this pull request Nov 7, 2022
* Rework Clients, Tools, and Data Prepper section

Signed-off-by: Naarcha-AWS <[email protected]>

* Add new Data Prepper files

Signed-off-by: Naarcha-AWS <[email protected]>

Signed-off-by: Naarcha-AWS <[email protected]>
(cherry picked from commit 4d6a275)

Co-authored-by: Naarcha-AWS <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
4 - Doc review PR: Doc review in progress 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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants