Migrating from Artifactory

relic import artifactory copies a JFrog Artifactory® into the Relic server you are signed in to: groups, local, remote and virtual repositories, permission targets, and local repositories' files with their properties. It only reads the source, through its REST API.

Preview the import:

relic import artifactory https://artifactory.example.com --user admin --password-stdin --dry-run

Run the import, with the password on standard input:

relic import artifactory https://artifactory.example.com --user admin --password-stdin

Import one repository, with an access token on standard input:

cat source.token | relic import artifactory https://artifactory.example.com --token-stdin --repository libs-release

Import from a source whose certificate comes from a private certificate authority, trusting that authority's certificate as well as the system's:

relic import artifactory https://artifactory.example.com --user admin --password-stdin --ca-file ca.crt

• Running again resumes or picks up changes. Existing repositories, groups and permissions stay unless --update; files Relic holds with the same SHA-256 are skipped.
• --repository limits repositories and files, not groups or permission targets. An unknown name fails the import before it copies anything.
• A virtual repository loses members that were not imported, with a note.
• Files are uploaded with the source's checksums, which Relic verifies.
• A federated repository becomes a local one, with a note. Federate it again with a replication.
• Users are not copied. Connect LDAP or create them again. A permission target loses its grants to users and groups Relic does not have, with a note; import again with --update once they exist.
• A repository whose project Relic does not have is copied without it, with a note.
• Remote caches are not copied; Relic fills them on demand.