Cloud Integration – Transporting packages regionwise

Motivation:

All packages are developed and validated in the Dev/QA tenant and now they need to be moved to Pre-prod and Prod tenants based on the region.

Solution

As of today, we only support manual transports of content packages between tenants and hence there is no means to ensure that content packages are transported to prod or test or pre-prod tenant based on a pre-defined categorization.

In order to ease this process, follow a nomenclature of the content package naming convention to include the region or project or any other categorization.

You may also add this information to the tag or description of the content package. During the manual transport, the name (or tags or description) of the package shall provide the guidance on which content package needs to be transported to which tenants.

Please note that in case of a configure-only content, changing the name, tag or description of the content package also marks the content as updated and hence you shall not receive any updates or update notifications to such content packages. In such cases, you can make use of the version suffix that gets added to the name when the content is copied from the discover view to the design view. This way the content name gets enriched with the categorization information without getting marked as updated.