Migration - JFrog CLI - Repository Properties Issue
Describe the bug
During the configuration migration process of an on-prem Artifactory instance to cloud, while we run the transfer-config command with JFrog CLI, the properties associated with the repositories are not reflecting/ migrated to the target cloud instance.
Current behavior
Performing JFrog CLI config transfer operation, the repository properties are not being migrated. There are no errors in the configuration migration process and all the repositories are migrated successfully. However, the properties (repository properties, not the properties associated with artifacts) are not transferred.
For example repository.owner, repository.team etc;
Reproduction steps
Using the JFrog CLI following commands were executed during migration process without any errors:
-
Installed the latest version of the JFrog CLI in source-server
-
Configured the source-server for JFrog CLI
jf c add source-server
- Configured the target-server for JFrog CLI
jf c add target-server
- Installed the transfer-plugin in source-server
jf rt transfer-plugin-install source-server
- Precheck before transfer
jf rt transfer-config source-server target-server --prechecks
- Configuration transfer
jf rt transfer-config source-server target-server --force
All the phases involved in the configuration transfer were successfully completed.
Expected behavior
The configuration migration is expected to transfer the properties of the repositories during the configuration migration process which are not more than 2.4K characters long as per the documentation.
JFrog CLI version
2.57.0
Operating system type and version
Ubuntu 22.04.4 LTS
JFrog Artifactory version
artifactory-pro-7.84.10
JFrog Xray version
NA