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

How to deal with the display_name issue in seeding

XMLWordPrintable

    • Product / Portfolio Work
    • False
    • Hide

      None

      Show
      None
    • False
    • Hide

      A doc describing the pros and cons of the options. And plans of how to roll out the change.

      Jira tickets to do the actual work

      Show
      A doc describing the pros and cons of the options. And plans of how to roll out the change. Jira tickets to do the actual work
    • Unset
    • None

      In V1 role seeding, the role is recognized by name in the config. If the name is updated in the config, there is no way for the seeding process to recognize the role. Therefore, we introduced the display_name.

      There are ways to overcome this:

      • Populate the uuids from stage/prod into the file and update seeding logic, might cause issue in ephemeral or not?
      • Or update the config to have two fields, e.g., old_name, new_name, and update the seeding logic. Have to deal with situation next time when seeding, new_name is the old name.
      • Or other ways

      Check if v2 role is already tracking the display_name

              Unassigned Unassigned
              rh-ee-zhzeng Jay Zeng
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: