Uploaded image for project: 'AeroGear'
  1. AeroGear
  2. AEROGEAR-1994

[APB] Update deprovision playbook to check and deconfigure for shared services

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Major Major
    • None
    • None
    • None

      if this is a shared service, deconfigure keycloak, and delete the resources in the local namespace
      This means removing

      • the configmap in the target namespace
      • secret in the target namespace
      • removing the public client created during the provision?
      • remove the realm in shared namespace?

      We should not remove the realm as we will not know if it is an active realm or being used by another client.

      Possibly, if we stored information in the encode binding during the provision that we created the realm,
      then we could check for the number of clients, if it is 0 we could then remove the realm. However I think
      It is safer to not remove the realm after it has been created given the possibility of it being shared.

            vchepeli_jira Vitalii Chepeliuk (Inactive)
            pbrookes@redhat.com Philip Brookes (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved:

                Estimated:
                Original Estimate - 2 days Original Estimate - 2 days
                2d
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 3 days
                3d