Uploaded image for project: 'COmanage'
  1. COmanage
  2. CO-1775

Deleting a CO does not call provisioners for contained models

    XMLWordPrintable

Details

    Description

      When deleting a CO, the expected behavior is for all provisioners of that CO to be able to clean up the back-end and remove relevant data.

      What seems to be happening is that all provisioner-targets are removed up front when deleting a CO, after which the relevant delete operations are not passed to the - no longer existing - provisioning targets.

      A similar problem occurs when removing a provisioning target. In that case, the plugin should be allowed to clean up the back-end as well. This behavior can then be re-used when deleting a CO.

      Currently, our LDAP back-end retains all the CO, CoPerson, CoGroup and other information long after the original CO was deleted, which severely clutters the LDAP. It will also cause problems in case a CO is recreated with the same DN.

       

      Attachments

        Issue Links

          Activity

            People

              benn.oshrin@at.internet2.edu Benn Oshrin
              michiel.uitdehaag@at.internet2.edu Michiel Uitdehaag
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated: