Documentation Center

Reapplying custom Content Delivery Add-ons

If you have developed custom Add-ons for Content Delivery, reapply them after you have upgraded the microservices that they extend. Perform this task for each of your custom Add-ons for Content Delivery.

Before you begin

You must have a copy of your Add-on ZIP file available, either as a resource with a URL (say in an S3 bucket) or as a physical file on your local file system.

Procedure

  1. If your Add-on extends Content Deployer and defines Pipeline elements, ensure that these elements do not have an ID that is already in use by the core Content Deployer or by any other Content Deployer Add-on.
  2. Restart the microservice that your Add-on extends, passing the path to the ZIP file by adding the following command line switch:
    --extension=URL

    where URL is the URL of the file you want to add. (Alternatively, if you have the file on your local file system, you can pass the local file system path to the file.)

  3. Test the functionality of your Add-on to verify that it continues to work with the upgraded microservice.