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

Support to display workspace feature configured with wildcard #186

Merged
merged 2 commits into from
Sep 25, 2023

Conversation

ruanyl
Copy link
Owner

@ruanyl ruanyl commented Sep 20, 2023

Description

  1. In workspace update page, support to display workspace feature configured with wildcard.
  2. Fixed an issue which generateWorkspacePermissionError return void
  3. Fixed an issue which workspace route validation failed due to missing permission mode in schema
  4. Hide feature configure panel for management workspace

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

@codecov-commenter
Copy link

codecov-commenter commented Sep 20, 2023

Codecov Report

Merging #186 (fe976fa) into workspace (e3b7da3) will increase coverage by 0.02%.
Report is 1 commits behind head on workspace.
The diff coverage is 100.00%.

@@              Coverage Diff              @@
##           workspace     #186      +/-   ##
=============================================
+ Coverage      66.09%   66.12%   +0.02%     
=============================================
  Files           3420     3420              
  Lines          65747    65753       +6     
  Branches       10590    10590              
=============================================
+ Hits           43456    43478      +22     
+ Misses         19650    19634      -16     
  Partials        2641     2641              
Flag Coverage Δ
Linux_1 30.42% <33.33%> (+<0.01%) ⬆️
Linux_2 55.12% <100.00%> (+0.07%) ⬆️
Linux_3 42.76% <33.33%> (+<0.01%) ⬆️
Linux_4 34.52% <33.33%> (+<0.01%) ⬆️

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

Files Changed Coverage Δ
src/core/public/chrome/chrome_service.tsx 91.42% <ø> (ø)
...c/core/public/chrome/ui/header/collapsible_nav.tsx 98.11% <ø> (ø)
...public/chrome/ui/header/collapsible_nav_header.tsx 60.00% <ø> (ø)
src/core/public/chrome/ui/header/header.tsx 75.00% <ø> (ø)
src/core/public/mocks.ts 59.09% <ø> (ø)
src/core/public/workspace/workspaces_service.ts 96.29% <ø> (+59.25%) ⬆️
...blic/application/opensearch_dashboards_services.ts 20.00% <ø> (ø)
...ction/objects_table/components/duplicate_modal.tsx 0.00% <ø> (ø)
...ment_section/objects_table/saved_objects_table.tsx 57.35% <ø> (ø)
src/core/public/core_system.test.mocks.ts 100.00% <100.00%> (ø)
... and 2 more

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

// expanded to array of individual feature id, if the feature hasn't changed, we will
// set the feature config back to the original value so that category wildcard won't
// expanded to feature ids
formData.features = defaultValues?.features ?? [];
Copy link
Collaborator

Choose a reason for hiding this comment

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

Is that means the wildcard match will be removed after add some new feature ids?

Copy link
Owner Author

Choose a reason for hiding this comment

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

Yes, that makes sense to me as that's what the user selected

Copy link
Collaborator

Choose a reason for hiding this comment

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

OK. Just wonder if we can support wildcard for the feature category level. Which means if user select a feature category, we will store wildcard feature rule. If they remove some one, we will change to feature ids.

Copy link
Owner Author

Choose a reason for hiding this comment

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

Sounds good to me, we could have an improvement ticket for this.

1. In workspace update page, support to display workspace feature
configured with wildcard.

2. Fixed an issue which generateWorkspacePermissionError return void

3. Fixed an issue which workspace route validation failed due to missing
   permission mode in schema

Signed-off-by: Yulong Ruan <ruanyl@amazon.com>
Signed-off-by: Yulong Ruan <ruanyl@amazon.com>
@ruanyl ruanyl force-pushed the feature/support-wildcard-on-ui branch from b0731a4 to fe976fa Compare September 25, 2023 05:39
@ruanyl ruanyl merged commit 25b9e5c into workspace Sep 25, 2023
21 of 41 checks passed
opensearch-workspace-development bot pushed a commit that referenced this pull request Sep 25, 2023
* Support to display workspace feature configured with wildcard

1. In workspace update page, support to display workspace feature
configured with wildcard.

2. Fixed an issue which generateWorkspacePermissionError return void

3. Fixed an issue which workspace route validation failed due to missing
   permission mode in schema

Signed-off-by: Yulong Ruan <ruanyl@amazon.com>

* update dependence array

Signed-off-by: Yulong Ruan <ruanyl@amazon.com>

---------

Signed-off-by: Yulong Ruan <ruanyl@amazon.com>
(cherry picked from commit 25b9e5c)
Signed-off-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