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

[DOC] Exploring data with Discover #2435

Merged
merged 40 commits into from
Feb 1, 2023
Merged

[DOC] Exploring data with Discover #2435

merged 40 commits into from
Feb 1, 2023

Conversation

vagimeli
Copy link
Contributor

@vagimeli vagimeli commented Jan 19, 2023

Signed-off-by: vagimeli [email protected]

Description

Create Discover homepage; creates new section and foundational user documentation

Issues Resolved

#751
#991
#2237
#1406
#1711
#1710

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.

Signed-off-by: vagimeli <[email protected]>
@vagimeli vagimeli requested a review from a team as a code owner January 19, 2023 16:51
@vagimeli vagimeli self-assigned this Jan 19, 2023
@vagimeli vagimeli requested a review from ananzh January 20, 2023 21:45
@vagimeli
Copy link
Contributor Author

@ananzh Will you review this new Discover documentation and provide your feedback? If possible, please complete the review by Tuesday, 1/24. Thank you :)

@vagimeli vagimeli added the 3 - Tech review PR: Tech review in progress label Jan 20, 2023
_dashboards/discover/index.md Outdated Show resolved Hide resolved
Copy link
Contributor

@alicejw1 alicejw1 left a comment

Choose a reason for hiding this comment

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

Excellent tutorial!

_dashboards/discover/multi-data-sources.md Outdated Show resolved Hide resolved
_dashboards/discover/multi-data-sources.md Outdated Show resolved Hide resolved
_dashboards/discover/index.md Outdated Show resolved Hide resolved
_dashboards/discover/index.md Outdated Show resolved Hide resolved
_dashboards/discover/index.md Outdated Show resolved Hide resolved
_dashboards/discover/index.md Outdated Show resolved Hide resolved
_dashboards/discover/index.md Outdated Show resolved Hide resolved
_dashboards/discover/index.md Outdated Show resolved Hide resolved
_dashboards/discover/index.md Outdated Show resolved Hide resolved
_dashboards/discover/index.md Outdated Show resolved Hide resolved
@vagimeli vagimeli added 4 - Doc review PR: Doc review in progress and removed 3 - Tech review PR: Tech review in progress labels Jan 27, 2023
@vagimeli vagimeli changed the title [DOC] Create Discover homepage [DOC] Using Discover Jan 30, 2023
@vagimeli vagimeli changed the title [DOC] Using Discover [DOC] Exploring data with Discover Jan 30, 2023
Signed-off-by: vagimeli <[email protected]>
Signed-off-by: vagimeli <[email protected]>
@vagimeli vagimeli requested a review from carolxob January 30, 2023 20:54
Signed-off-by: vagimeli <[email protected]>
Signed-off-by: vagimeli <[email protected]>
Copy link
Contributor

@carolxob carolxob left a comment

Choose a reason for hiding this comment

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

Looks great!

Signed-off-by: vagimeli <[email protected]>
Signed-off-by: vagimeli <[email protected]>
@vagimeli vagimeli merged commit d67fa6b into main Feb 1, 2023
@vagimeli vagimeli added Closed - Complete Issue: Work is done and associated PRs closed v2.5.0 'Issues and PRs related to version v2.5.0' backport 2.5 PR: Backport label for 2.5 and removed 6 - Done but waiting to merge PR: The work is done and ready to merge labels Feb 1, 2023
opensearch-trigger-bot bot pushed a commit that referenced this pull request Feb 1, 2023
Creates new documentation website page and Discover content.
---------

Signed-off-by: vagimeli <[email protected]>
(cherry picked from commit d67fa6b)
@vagimeli vagimeli added backport 1.3 PR: Backport label for v1.3.x 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 labels Feb 1, 2023
@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-2435-to-2.1
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 d67fa6bd4e077fbc31a9e4c0695dc59e84846769
# Push it to GitHub
git push --set-upstream origin backport/backport-2435-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-2435-to-2.1.

@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
cd .worktrees/backport-2.4
# Create a new branch
git switch --create backport/backport-2435-to-2.4
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 d67fa6bd4e077fbc31a9e4c0695dc59e84846769
# Push it to GitHub
git push --set-upstream origin backport/backport-2435-to-2.4
# Go back to the original working tree
cd ../..
# 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-2435-to-2.4.

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

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

@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
cd .worktrees/backport-2.3
# Create a new branch
git switch --create backport/backport-2435-to-2.3
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 d67fa6bd4e077fbc31a9e4c0695dc59e84846769
# Push it to GitHub
git push --set-upstream origin backport/backport-2435-to-2.3
# Go back to the original working tree
cd ../..
# 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-2435-to-2.3.

@opensearch-trigger-bot
Copy link
Contributor

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

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

@vagimeli vagimeli added backport 2.4 PR: Backport label for 2.4 and removed backport 1.3 PR: Backport label for v1.3.x 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 labels Feb 1, 2023
@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
cd .worktrees/backport-2.4
# Create a new branch
git switch --create backport/backport-2435-to-2.4
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 d67fa6bd4e077fbc31a9e4c0695dc59e84846769
# Push it to GitHub
git push --set-upstream origin backport/backport-2435-to-2.4
# Go back to the original working tree
cd ../..
# 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-2435-to-2.4.

vagimeli added a commit that referenced this pull request Feb 2, 2023
Creates new documentation website page and Discover content.
---------

Signed-off-by: vagimeli <[email protected]>
(cherry picked from commit d67fa6b)

Co-authored-by: Melissa Vagi <[email protected]>
Naarcha-AWS pushed a commit that referenced this pull request Feb 2, 2023
Creates new documentation website page and Discover content.
---------

Signed-off-by: vagimeli <[email protected]>
@vagimeli vagimeli deleted the create-discover-homepage branch February 9, 2023 18:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport 2.4 PR: Backport label for 2.4 backport 2.5 PR: Backport label for 2.5 Closed - Complete Issue: Work is done and associated PRs closed v2.5.0 'Issues and PRs related to version v2.5.0'
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants