Overview
In addition to general support for advanced artifact management, Artifactory support for Vagrant provides:
Distribution and sharing of Vagrant boxes within your organization.
Calculation of Metadata for Vagrant boxes hosted in Artifactory's local repositories
Extensive security features that give you fine-grained access control over boxes.
Support for flexible repository layouts that allow you to organize your boxes and assign access privileges according to projects or development teams.
Smart searches for boxes.
Configuration
Local Repositories
To create a local Vagrant repository to host your Vagrant boxes, from the Administration module go to Repositories | Repositories | Local and create a new Local Repository and set Vagrant as the Package Type.
 |
Deploying Vagrant Boxes
Deploying a package using the UI
To deploy a Vagrant box to Artifactory, in the Application module, under Artifactory | Artifacts select the repository to which you want to deploy your Vagrant box and click Deploy.
The Deploy dialog is displayed with your selected repository as the Target Repository and a default Target path.
 |
You can add properties you wish to attach to your box as parameters to the target path.
For example, to upload the box precise64-virtualbox-1.0.0.box, and specify that its name is precise64, with a provider of virtualbox and the version is 1.0.0, you would enter:
Specifying the Target Path
/precise64-virtualbox-1.0.0.box;box_name=precise64;box_provider=virtualbox;box_version=1.0.0
Set Me Up
You can also select your repository and click Set Me Up to view the cURL command you can use to upload your box.
 |
Be careful with spaces
Make sure you don't enter any superfluous spaces in the Target Path specification.
Once you have deployed your Vagrant box, and Artifactory has recalculated the repository index, your repository should be organized as displayed below:
 |
Deploying a package using Matrix Parameters
You can also deploy Vagrant boxes to Artifactory with an explicit URL using Matrix Parameters.
The URL is built similarly to the Target Path format as follows:
Deploying a package using Matrix Parameters
PUT "http://{Artifactory URL}/{vagrantRepoKey}/{vagrantBoxName.box};box_name={name};box_provider={provider};box_version={version}" For example, to upload the box precise64-virtualbox-1.0.0.box, and specify that it's name is precise64, with a provider of virtualbox and the version is 1.0.0, you would enter:
Example
PUT "http://localhost:8080/artifactory/vagrant-local/precise64-virtualbox-1.0.0.box;box_name=precise64;box_provider=virtualbox;box_version=1.0.0"
Setting the Target Path
The Target Path can be anywhere in the repository, but it has to contain the 3 mandatory matrix parameters: box_name, box_provider and box_version and the file name must end with .box. The format is as follows:
Target Path Format
PUT "http://{Artifactory URL}/{vagrantRepoKey}/{path/to/vagrantBoxName.box};box_name=[name];box_provider=[provider];box_version=[version]"Parameter | Description |
|---|---|
name | The value to assign to the |
provider | The value to assign to the box |
version | The value to assign to the |
Provisioning Vagrant Boxes
Vagrant boxes are available through the following URL:
Vagrant box URL
vagrant box add "http://{Artifactory URL}/api/vagrant/{vagrantRepoKey}/{boxName}"Specifying the path to the box
With Vagrant client commands, make sure you don't specify the path to a box in the command. The path should be specified using properties.
For example, to provision a Vagrant box calledprecise64from a repository calledvagrant-local, you would construct it's name in the following manner:
Provisioning a Vagrant box
vagrant box add "http://localhost:8080/artifactory/api/vagrant/vagrant-local/precise64"
You can select the repository from which you want to provision your box, and click Set Me Up to get the specific URL for the selected repository.
You can also, optionally, pass parameters to specify a specific box version or provider. For example:
Provisioning a Vagrant box by version
vagrant box add "http://localhost:8080/artifactory/api/vagrant/vagrant-local/precise64 --provider virtualbox --box-version 1.0.0"
In addition, boxes can be provisioned using properties; this is useful when you want to download the latest box tagged by a specific property.
The properties query parameter value should comply with Using Properties in Deployment and Resolution.
Examples:
Provisioning a Vagrant box by version
vagrant box add "http://localhost:8080/artifactory/api/vagrant/vagrant-local/precise64?properties=box_version%2B=3.0.0"
Note the '%2B' encoding on the command for the '+' symbol (which is for Mandatory properties: key+=value)
The following example downloads a box with box_name=trusty64, box_version=3.0.0 from path="folder".
It uses an optional "path" property ( in addition to the mandatory properties) to specify the path where the box is stored in Artifactory. We will use this property for resolution of the box.
vagrant box add "http://localhost:8080/artifactory/api/vagrant/vagrant-local/trusty64?properties=box_version%2B=3.0.0;path%2B=folder"
Note the format for resolution of multiple properties: key1+=value1;key2+=value2....
 |
Authenticated Access to Servers
If you need to access a secured Artifactory server that requires a username and password, you need to specify 2 environment variables:
ATLAS_TOKEN
This token is a Base64 encoded string of the user credentials (formatted
username:password).From Artifactory 725.7, you will need to create an Access Token via the JFrog Platform UI and use that token to authorize Vagrant access.
VAGRANT_SERVER_URL - The base URL for the Artifactory server.
Setting ATLAS_TOKEN and VAGRANT_SERVER_URL
export ATLAS_TOKEN={token}
export VAGRANT_SERVER_URL=http://{Artifactory URL}/api/vagrant/{vagrantRepoKey}
For example:
export ATLAS_TOKEN=YWRtaW46QVAzWGhzWmlDU29NVmtaQ2dCZEY3XXXXXXXX
export VAGRANT_SERVER_URL=http://localhost:8081/api/vagrant/vagrant-localBoth environment variables are required
When using Artifactory with authenticated access (i.e. anonymous access is disabled), both of these environment variables are required. If either of them is not set, the Vagrant client will not be able to access Artifactory and a 401 error message will be generated.