When a domain is marked for deletion, the job DeleteDomainReferences deletes all references to that domain. Similarly, if a user is marked for deletion, the job DeleteUserReferences deletes all references to that user. Currently, the configured DomainDeletionPipeline
or the corresponding UserDeletionPipeline
are called in each cartridge. These pipeline calls still work, but they have been marked as deprecated and will be removed. Instead, use the Guice Multibinder to bind DomainReferenceDeletionHandler
or accordingly UserReferenceDeletionHandler
as described in Concept - Mass Data Cleanup.
The migration is only needed if DomainDeletionPipeline
is used in the cartridge.
In the cartridge properties file, remove the DomainDeletionPipeline
configuration.
Afterwards, add and bind a cartridge-specific domain reference deletion handler as described in Cookbook - Mass Data Cleanup | Recipe: Add and Bind a Cartridge-Specific Domain Reference Deletion Handler, which is the replacement for the removed pipeline from the properties file. In that new domain reference deletion handler, you can migrate the previous pipeline execution for the domain reference deletion handling of the cartridge.
The migration is only needed if UserDeletionPipeline
is used in the cartridge.
In the cartridge properties file, remove the UserDeletionPipeline
configuration.
Afterwards, add and bind a cartridge-specific user reference deletion handler similar to domains as described in Cookbook - Mass Data Cleanup | Recipe: Add and Bind a Cartridge-Specific Domain Reference Deletion Handler, which is the replacement for the removed pipeline from the properties file. In that new user reference deletion handler, you can migrate the previous pipeline execution for the user reference deletion handling of the cartridge.