Import Configuration

Different Artifactory instances may serve different groups of people, each with their own special requirements for artifact management. However, there are several aspects of your Artifactory configuration that you can keep uniform. For example, your local repository for Maven releases might be called libs-release-local on all Artifactory instances. Similarly, for development with node.js, you might have the following three repositories defined on all Artifactory instances: npm-local, npm-remote, and npm-virtual. In a similar way, you might have a standard set of permission targets, property sets, LDAP settings, LDAP groups and more.

Maintaining some uniformity in how your Artifactory instances are configured offers several benefits. Monitoring your instances is easier because anything that is out of place will be easier to notice. Managing your instances is also easier because in many cases you know the name of the setting you want to update, and you know its configuration parameters. There’s no need to drill down into different Artifactory instances and see what their LDAP settings is called, or what their Docker Hub proxy is called, for example.

To facilitate replication of one Artifactory configuration to another Artifactory instance, Mission Control lets you import the configuration from the source instance into a configuration script. The script created is like any other, and can be tweaked as needed. Once imported and tweaked, the script is available to be applied to any other Artifactory instance effectively letting you replicate the configuration from the source instance.