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

Remove public workspace logic for share API #149

Merged
merged 1 commit into from
Sep 14, 2023

Conversation

Hailong-am
Copy link
Collaborator

Description

Issues Resolved

Screenshot

Testing the changes

Check List

  • All tests pass
    • yarn test:jest
    • yarn test:jest_integration
    • yarn test:ftr
  • New functionality includes testing.
  • New functionality has been documented.
  • Update CHANGELOG.md
  • Commits are signed per the DCO using --signoff

@wanglam
Copy link
Collaborator

wanglam commented Sep 13, 2023

@Hailong-am Is that means for saved objects with PUBLIC workspace can be shared to other workspaces?

@codecov-commenter
Copy link

codecov-commenter commented Sep 13, 2023

Codecov Report

Merging #149 (ad7eca2) into workspace (05fab00) will increase coverage by 0.01%.
The diff coverage is 0.00%.

@@              Coverage Diff              @@
##           workspace     #149      +/-   ##
=============================================
+ Coverage      65.71%   65.73%   +0.01%     
=============================================
  Files           3336     3336              
  Lines          64657    64656       -1     
  Branches       10318    10316       -2     
=============================================
+ Hits           42488    42500      +12     
+ Misses         19590    19577      -13     
  Partials        2579     2579              
Flag Coverage Δ
Linux_1 34.74% <ø> (ø)
Linux_3 42.54% <0.00%> (+<0.01%) ⬆️
Linux_4 34.70% <0.00%> (+<0.01%) ⬆️
Windows_1 34.80% <ø> (+0.04%) ⬆️
Windows_2 54.67% <0.00%> (+<0.01%) ⬆️
Windows_3 42.55% <0.00%> (+<0.01%) ⬆️
Windows_4 34.70% <0.00%> (+<0.01%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files Changed Coverage Δ
src/core/server/saved_objects/routes/index.ts 100.00% <ø> (ø)
src/core/server/saved_objects/routes/share.ts 12.50% <0.00%> (ø)
...ore/server/saved_objects/service/lib/repository.ts 78.53% <0.00%> (+0.13%) ⬆️
...rver/saved_objects/service/saved_objects_client.ts 55.17% <0.00%> (ø)

... and 1 file with indirect coverage changes

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

@Hailong-am
Copy link
Collaborator Author

@Hailong-am Is that means for saved objects with PUBLIC workspace can be shared to other workspaces?

As we don't have any special logic for public workspace, based on that i removed the limitation for public workspace.

Signed-off-by: Hailong Cui <ihailong@amazon.com>
@Hailong-am Hailong-am merged commit aa51f84 into ruanyl:workspace Sep 14, 2023
@opensearch-workspace-development

The backport to workspace-2.9 failed:

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

To backport manually, run these commands in your terminal:

# Navigate to the root of your repository
cd $(git rev-parse --show-toplevel)
# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/OpenSearch-Dashboards/backport-workspace-2.9 workspace-2.9
# Navigate to the new working tree
pushd ../.worktrees/OpenSearch-Dashboards/backport-workspace-2.9
# Create a new branch
git switch --create backport/backport-149-to-workspace-2.9
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 aa51f8420cc1c746f4ac9c9c4e3a08130410f40b
# Push it to GitHub
git push --set-upstream origin backport/backport-149-to-workspace-2.9
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/OpenSearch-Dashboards/backport-workspace-2.9

Then, create a pull request where the base branch is workspace-2.9 and the compare/head branch is backport/backport-149-to-workspace-2.9.

@opensearch-workspace-development

The backport to workspace-2.9 failed:

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

To backport manually, run these commands in your terminal:

# Navigate to the root of your repository
cd $(git rev-parse --show-toplevel)
# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/OpenSearch-Dashboards/backport-workspace-2.9 workspace-2.9
# Navigate to the new working tree
pushd ../.worktrees/OpenSearch-Dashboards/backport-workspace-2.9
# Create a new branch
git switch --create backport/backport-149-to-workspace-2.9
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 aa51f8420cc1c746f4ac9c9c4e3a08130410f40b
# Push it to GitHub
git push --set-upstream origin backport/backport-149-to-workspace-2.9
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/OpenSearch-Dashboards/backport-workspace-2.9

Then, create a pull request where the base branch is workspace-2.9 and the compare/head branch is backport/backport-149-to-workspace-2.9.

opensearch-workspace-development bot pushed a commit that referenced this pull request Sep 14, 2023
Signed-off-by: Hailong Cui <ihailong@amazon.com>
(cherry picked from commit aa51f84)
Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
ruanyl pushed a commit that referenced this pull request Sep 15, 2023
Signed-off-by: Hailong Cui <ihailong@amazon.com>
SuZhou-Joe pushed a commit that referenced this pull request Sep 16, 2023
Signed-off-by: Hailong Cui <ihailong@amazon.com>
Hailong-am pushed a commit that referenced this pull request Sep 18, 2023
(cherry picked from commit aa51f84)

Signed-off-by: Hailong Cui <ihailong@amazon.com>
Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants