Observe the guidelines below when defining path mappings for distributed Release Bundle v2 versions to Edge nodes.
When the enhanced distribution engine is not activated or not available (before release 2.28.x)
You can define path mapping only during the first distribution or export of a Release Bundle version.
Each distribution target must use the same path mapping.
Once a path mapping has been defined, it cannot be changed afterward.
When the enhanced distribution engine is available and activated (release 2.28.x or later)
Note
For more information about the enhanced distribution engine, see Distribution 2.28.1.
Each distribution operation can have one defined path mapping.
You can define different path mappings for each distribution target by executing multiple distribution operations.
The path mapping functionality described above does not apply to exported archives in air-gap environments in the current version.
Once you define path mappings to a target you cannot define a different set of path mappings for the same Release Bundle version to that target.
You can use the REST API to redistribute a Release Bundle version to a target that already has that version provided the path mapping has not changed. If the path mapping has changed, you must first delete the Release Bundle version from the target before redistributing it. When using the platform UI, you must delete the Release Bundle version before redistributing it even when the path mapping has not changed.
After activating the enhanced distribution engine, you must create a new version of Release Bundles that were distributed before activation before they can be redistributed.
If the enhanced distribution engine is activated and later deactivated, you must create a new version of Release Bundles that were distributed during activation before they can be redistributed.
Enhanced distribution features are available only when the source Artifactory and all Edge nodes have been upgraded to Artifactory 7.101.x or later and Distribution 2.28.x or later. If you try distributing a Release Bundle version to a mix of upgraded and non-upgraded Edge nodes, the operation will fail.