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

[SPIKE] Migrate non-workspace resource definition

XMLWordPrintable

    • Product / Portfolio Work
    • False
    • Hide

      None

      Show
      None
    • False
    • None
    • Unset
    • None

      Currently are migrated only resource definitions with "group.id".

      This was done by this condition: https://github.com/RedHatInsights/insights-rbac/blob/ba0df0f7c6f14e7a515c504b94fae5977d2dca19/rbac/migration_tool/sharedSystemRolesReplicatedRoleBindings.py#L121

      We need to migrate rest of resource definitions, prod data[1].

      This spike needs to determine how other resource definitions will be migrated.

      [1]https://docs.google.com/spreadsheets/d/14XcyZJxI27z53FefvFiJ2GvbgicYkTQFh_ghI5D02-U/edit?gid=0#gid=0

       

      Related Slack Conversation: https://redhat-internal.slack.com/archives/C059NUD49PD/p1756479485414499

       

      Goals

      1. Create same spreadsheet like [1] with latest data - it is enough only with Filtered and UnFiltered Permissions
      2. Identify ALL permissions and services which uses resource definitions in role access with attribute filters different then "group.id" (prod)
      3. From this list of services which are NOT related to M5 create epic which will track migration on service by service basis. This SPIKE can be placed in mentioned EPIC
      4. From this list of services which are related to M5:
        1. Determine a way how those resource will be migrated and prepare tickets or documentation to prepare tickets
        2. Put those tickets into new epic from 3.

              Unassigned Unassigned
              lpichler@redhat.com Libor Pichler
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: