jf rt transfer-config-merge
Merge projects and repositories from a source Artifactory instance to a target instance when no conflicts exist.
Synopsis
jf rt transfer-config-merge <source-server-id> <target-server-id> [options]
Aliases: —
Arguments
| Argument | Required | Description |
|---|---|---|
<source-server-id> | Yes | Server ID to export configuration from |
<target-server-id> | Yes | Server ID to import configuration to |
Options
| Flag | Default | Description |
|---|---|---|
--exclude-projects | — | Semicolon-separated list of JFrog Projects to exclude. Supports wildcards |
--exclude-repos | — | Semicolon-separated list of repositories to exclude. Supports wildcards |
--include-projects | — | Semicolon-separated list of JFrog Project keys to include. Supports wildcards |
--include-repos | — | Semicolon-separated list of repositories to include. Supports wildcards |
Examples
Merge Configuration
jf rt transfer-config-merge --helpMerge Specific Repositories
jf rt transfer-config-merge source-server target-server --include-repos "libs-release;libs-snapshot"Merge Specific Projects
jf rt transfer-config-merge source-server target-server --include-projects "my-project;other-project"Exclude Repositories and Projects
jf rt transfer-config-merge source-server target-server --exclude-repos "temp-*" --exclude-projects "test-*"Note: Merging only adds new configuration. Existing target configuration is not overwritten when conflicts exist.
When to Use
Use transfer-config-merge when you want to add repositories and projects from one Artifactory to another without wiping the target. This is the safe alternative to transfer-config when the target already has data.
Choose this vs alternatives:
| Scenario | Command |
|---|---|
| Target is empty, full migration | jf rt transfer-config |
| Target has data, merge safely | jf rt transfer-config-merge (this command) |
| Config already transferred, move files | jf rt transfer-files |
Important Notes
- The merge only adds new configuration. If a repository or project with the same key already exists on the target, it is not overwritten — the conflict is skipped.
- Use
--include-reposand--include-projectsto selectively merge specific items. - Wildcards are supported in repository and project filters (e.g.,
libs-*,team-*).
Updated about 1 month ago
