Uploaded image for project: 'Hybrid Cloud Console'
  1. Hybrid Cloud Console
  2. RHCLOUD-40433

Create new action move workspace

XMLWordPrintable

    • Product / Portfolio Work
    • 5
    • False
    • Hide

      None

      Show
      None
    • False
    • None
    • Unset
    • None
    • Plat-Ex UI Sprint 41

      Description

      As a customer I should be able to move WS between workspaces by using new action on a row called "Move Workspace".

      Technical details

      This action is only enabled if the user has write access to the workspace checked by permissions check.

       

      This feature will use the new Workspace selector.

       

      The action will show new modal with title: Move workspace $CURRENT_WS_NAME then we will show breadcrumbs component which will have first item clickable $WS_PARENT_NAME and second item will be workspace selector.

       

      Hide this feature behind a feature flag `platform.rbac.workspace-hierarchy` or `platform.rbac.workspaces` (either of them can be enabled)

       

      Based on the table in https://issues.redhat.com/browse/CRCPLAN-310 user can perform these actions:

      WS type Move
      Root
      Default
      Ungroupped
      Standard

      If the action is allowed for workspace type we first have to check permissions list by calling getPermissions from chrome API. If the user has inventory:groups:write with empty resource array they should have the action allowed. If the user has any resource definition only workspaces with matching ID should be allowed.

      If the action is either not allowed based on the type and or not allowed based on the resource definition permission we should disable the action in the dropdown.

       

      There is already similar check for edit and remove actions so we can utilize that implementation.

              aferdina@redhat.com Alexandra Ferdinand
              khala-1 Karel Hala
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: