APP-4658 - Add path-mapping flags to version-promote and version-release

[danielreJfrog]

Summary

• Add --map-in, --map-out, and --map-type flags to version-promote and version-release commands
• Enable regex-based artifact path transformations during promotion/release operations
• Mappings are forwarded as modifications.mappings in the request body to the Bundle Handler Service

Usage

# Single mapping
jf at version-promote my-app 1.0.0 PROD \
  --map-type=".*" --map-in="(.*)" --map-out="stable-release/$1"

# Multiple mappings (semicolon-separated)
jf at version-promote my-app 1.0.0 PROD \
  --map-in="(.*);(.*\.jar)" \
  --map-out="release/$1;jars/$1" \
  --map-type=".*;maven"

Changes

File	Change
model/promote_app_version_request.go	Add PromotionPathMapping, PromotionModifications types and Modifications field to CommonPromoteAppVersion
commands/flags.go	Add --map-in, --map-out, --map-type flag definitions
commands/version/version_utils.go	Add ParsePathMappings() function
commands/version/promote_app_version_cmd.go	Wire path mappings into promote payload
commands/version/release_app_version_cmd.go	Wire path mappings into release payload
model/release_app_version_request.go	Accept modifications parameter in constructor
*_test.go	Unit tests for ParsePathMappings and updated existing tests

Test plan

• Unit tests for ParsePathMappings covering: single/multiple mappings, partial package types, error cases (mismatched counts, missing flags)
• Existing tests updated to compile with new constructor signature
• E2E: jf at version-promote with --map-in and --map-out sends correct request body

Jira

APP-4658

Made with Cursor

[github-actions]

Test Results

54 tests  +2   51 ✅ ±0   4m 49s ⏱️ -53s
 2 suites ±0    3 💤 +2 
 1 files   ±0    0 ❌ ±0 

Results for commit 56ba666. ± Comparison against base commit 2ce9356.

♻️ This comment has been updated with latest results.

[asafgabai]

The practice of requiring both list flags with the same length is very uncommon and makes the command much more complex to read and write.
Taking into account the fact that the length of --map-type can be smaller than the others making it even more confusing and unclear.
The existing --source-type-* flags show a cleaner approach:

--source-type-packages="type=npm, name=@gpizza/pizza-frontend, version=1.0.0, repo-key=tests-npm-local; type=npm, name=@gpizza/green-pizza, version=2.0.1"

Another option is to limit the path mappings to 1 in the CLI (AFAIK that's the situation in Distribution's path mappings).
Consider discussing this with the product.