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

[SPIKE] Disable v1 apis for orgs using v2

XMLWordPrintable

    • False
    • Hide

      None

      Show
      None
    • False
    • Hide

      Orgs with the v2 edit enabled get rejected when calling v1 write apis

      Show
      Orgs with the v2 edit enabled get rejected when calling v1 write apis
    • Unset
    • None

      For orgs start using v2 edit apis, we should not allow them to continue using v1 apis, or things might get messed up.

      kwalsh@redhat.com mentioned that there is a feature flag for UI to identify this. We can reuse this feature flag to gate our v1 apis (check v1 flag before the call can execute)

      Flag from UI: https://docs.google.com/document/d/1WXxV45RKN1N8nq-cALBqk6acJY-1Nhd5mzm33P7exew/edit?tab=t.0#bookmark=id.jcsdvqwsowy

      Make a list of apis that needs to be considered, e.g., we are still using v1 adding users to groups

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

                Created:
                Updated: