1. In the Administration module, under Repositories | Repositories | Remote, click New Remote Repository. 
2. Select Chef from the Select Package Type dialog.
3. In the New Repository dialog, set the Repository Key value, and specify the URL to the remote repository in the URL field as displayed below.
   
4. Click Save & Finish.

Virtual Chef Supermarket

A Virtual Repository defined in Artifactory aggregates packages from both local and remote repositories.
This allows you to access both locally hosted Chef Cookbook packages and remote proxied Chef Cookbook repositories from a single URL defined for the virtual repository.

To define a virtual Chef Cookbook repository, create a Virtual Repositories, select Chef from the Select Package Type dialog, and select the underlying local and remote Chef repositories to include in the Basic settings tab.

Using the Knife Command Line

To use the Knife command line you need to make sure it's installed. It's part of ChefDK, that can be installed in various ways.

Once you have created your Chef supermarket, you can select it in the Tree Browser and click Set Me Up to get code snippets you can use to change your Chef supermarket URL, and deploy and resolve packages using the knife command line tool.

Set the default Chef supermarket with a URL pointing to a Chef supermarket in Artifactory by editing your ~/.chef/knife.rb configuration file (the example below uses a repository with the key chef-virtual). You authenticate the request using your username and password or with your Artifactory API key :

knife[:supermarket_site] = 'http://admin:password@localhost:8081/artifactory/api/chef/chef-virtual'
or
knife[:supermarket_site] = 'http://admin:<APIKEY>@localhost:8081/artifactory/api/chef/chef-virtual'

Working with Artifactory without Anonymous Access

By default, Artifactory allows Anonymous Access for Chef repositories. This is defined under Security | General Configuration. For details please refer to Allow Anonymous Access.
If you want to be able to trace how users interact with your repositories you need to uncheck the Allow Anonymous Access setting. This means that users will be required to enter their username and password.

The Knife command line tool does not support basic authentication (it only supports authentication with RSA keys).
To enable basic authentication, you will need to install the knife-art.gem plugin.

chef gem install knife-art

If properly installed you should see the following specific Artifactory commands:

** ARTIFACTORY COMMANDS **
knife artifactory download COOKBOOK [VERSION] (options)
knife artifactory install COOKBOOK [VERSION] (options)
knife artifactory list (options)
knife artifactory search QUERY (options)
knife artifactory share COOKBOOK [CATEGORY] (options)
knife artifactory show COOKBOOK [VERSION] (options)
knife artifactory unshare COOKBOOK VERSION

These commands are a wrapper around the standard Knife supermarket commands, that enable basic authentication. To add these credentials, pre-pend them to the URL of the Chef supermarket configured in your knife.rb file:

knife[:supermarket_site] = 'http://admin:password@localhost:8081/artifactory/api/chef/chef-virtual'

Publishing Cookbooks

You can use the UI or a simple REST API call to upload the tgz/tar.gz containing the Cookbook to a Chef repository.

Artifactory will automatically extract the relevant information from the metadata.json to later serve the index and respond properly to client calls. This metadata.json file is mandatory. If it does not exist in your cookbook, you can use a Knife command to generate it and then publish it to Artifactory. For example:

$ chef generate cookbook myapp
$ knife artifactory share myapp tool

Using the Berkshelf Command Line

Berkshelf is a dependency manager for Chef Cookbooks, and is a part of the ChefDK.

To resolve dependencies from a Chef supermarket in Artifactory, first configure your Artifactory API Key using config.rb:

artifactory_api_key "<APIKEY>"

source artifactory: 'http://localhost:8081/artifactory/api/chef/chef-virtual'

vagrant@default-ubuntu-1404:~/chef-zero/mycookbook$ berks
Resolving cookbook dependencies...
Fetching 'mycookbook' from source at .
Fetching cookbook index from http://localhost:8081/artifactory/api/chef/chef-virtual...
Installing apt (5.0.0) from http://localhost:8081/artifactory/api/chef/chef-virtual ([opscode] http://localhost:8081/artifactory/api/chef/chef-virtual/api/v1)
Installing chef-apt-docker (1.0.0) from http://localhost:8081/artifactory/api/chef/chef-virtual ([opscode] http://localhost:8081/artifactory/api/chef/chef-virtual/api/v1)
Installing chef-yum-docker (1.0.1) from http://localhost:8081/artifactory/api/chef/chef-virtual ([opscode] http://localhost:8081/artifactory/api/chef/chef-virtual/api/v1)
Installing compat_resource (12.16.2) from http://localhost:8081/artifactory/api/chef/chef-virtual ([opscode] http://localhost:8081/artifactory/api/chef/chef-virtual/api/v1)
Using mycookbook (0.1.0) from source at .
Installing yum (4.1.0) from http://localhost:8081/artifactory/api/chef/chef-virtual ([opscode] http://localhost:8081/artifactory/api/chef/chef-virtual/api/v1)

Viewing Individual Chef Cookbook Information

Artifactory lets you view selected metadata of a Chef Cookbook directly from the UI.

In the Application module, Artifactory | Artifacts tab, Tree Browser, drill down to select the tgz/tar.gz file you want to inspect. The metadata is displayed in the Chef Info tab.

Searching Chef Cookbooks

Artifactory supports a variety of ways to search for artifacts.
Artifactory also supports knife search [search terms ...]:


• For local repositories, it will look for the given terms in the name, description and maintainer fields.
• For remote repositories, the search will be done on the local cache, then the search query will be forwarded to the external repository and the results merged before returned to the client.
• For virtual repositories, the search will be done on local repositories and then on remote repositories, the results merged before returning to the client.