Adoptable Cookbooks List

Looking for a cookbook to adopt? You can now see a list of cookbooks available for adoption!
List of Adoptable Cookbooks

Supermarket Belongs to the Community

Supermarket belongs to the community. While Chef has the responsibility to keep it running and be stewards of its functionality, what it does and how it works is driven by the community. The chef/supermarket repository will continue to be where development of the Supermarket application takes place. Come be part of shaping the direction of Supermarket by opening issues and pull requests or by joining us on the Chef Mailing List.

Select Badges

Select Supported Platforms


artifact-deployer (17) Versions 0.8.2

A Chef Cookbook that provides a simple way to download, unpack and configure artifacts

cookbook 'artifact-deployer', '= 0.8.2'
cookbook 'artifact-deployer', '= 0.8.2', :supermarket
knife supermarket install artifact-deployer
knife supermarket download artifact-deployer
Quality 0%

Artifact Deployer

Build Status

A Chef Cookbook that provides a simple way to download, unpack and patch artifacts. Download is offered via - Maven GAV coordinates - HTTP Url - File-system path - S3 (file copy and bucket sync)

Artifact sources

Configuration is done via Chef JSON attributes; hereby are examples for each source type.

Maven artifacts

"artifacts": {
  "alfresco": {
      "enabled": true,
      "groupId": "org.alfresco",
      "artifactId": "alfresco",
      "type": "war",
      "version": "5.0.a",
      "destination": "/var/lib/tomcat7/webapps",
      "owner": "tomcat7"

Downloads alfresco WAR artifact and copies as /var/lib/tomcat7/webapps/alfresco.war

You can add Maven Repositories as artifact sources defining maven_repos databag item, as follows: { "id" : "my-repo", "url" : "", "username" : "user", "password" : "pwd" } Check [test maven_repos](test/integration/data_bags/maven_repos) databags for more samples.


"artifacts": {
  "junit": {
    "enabled": true,
    "url": "",
    "destination": "/var/lib/tomcat7/lib",
    "owner": "tomcat7"

Downloads junit-4.9.jar and copies as /var/lib/tomcat7/lib/junit.jar

File-system path

"artifacts": {
  "my-local-zip": {
    "enabled": true,
    "path": "/root/folder/",
    "destination": "/opt",
    "owner": "myuser"

Copies /root/folder/ into /opt/


If you want to sync a bucket with a local folder "artifacts": { "my-s3-bucket-folder": { "enabled": true, "s3_bucket" : "artifact-deployer-test", "destination": "/opt", "owner": "myuser" } } Creates /opt/my-s3-bucket-folder directory with all s3://artifact-deployer-test bucket contents in it

If you want to sync a bucket with a local folder "artifacts": { "my-s3-zip": { "enabled": true, "s3_bucket" : "artifact-deployer-test", "s3_filename" : "", "destination": "/opt", "owner": "myuser" } } Downloads from s3://artifact-deployer-test bucket and copies as /opt/

You can specify AWS key and secret defining awscli databag item, as follows: { "id" : "my-credentials", "aws_access_key_id" : "AKI*****************", "aws_secret_access_key" : "****************************************" } Check [test awscli](test/integration/data_bags/awscli) databags for more samples.

Unpacking and filtering

"artifacts": {
  "solr-home": {
    "enabled": true,
    "groupId": "org.alfresco",
    "artifactId": "alfresco-solr",
    "type": "zip",
    "version": "5.0.a",
    "destination": "/var/lib/tomcat7",
    "owner": "tomcat7",
    "unzip": true,
    "filtering_mode" : "replace",
    "properties" : {
      "archive-SpacesStore/conf/" : [
        "" : "",
        "solr.secureComms" : "none"
      "" : [
        "" : "",
        "filtering_mode" : "append"
    "terms" : {
      "context.xml" : [
        "@@ALFRESCO_HOST@@" : ""

Filtering can be used via terms or properties attributes defined within the artifact configuration; each of those contain a list of file path(String) => attributes(Map<String,String>), where - file path is the path, within the unpacked ZIP file, of the file that needs to be patched - attributes maps the original string with the new ones to be injected

When using terms, each attribute's key is replaced with the attribute's value.

When using properties, a file line starting with <key>= will be searched and replaced with <key>=<value>; if the line doesn't exist, by default nothing will happen (unless filtering_mode is set to append); if the file doesn't exist, it will be created.

filtering_mode can be specified at artifact level or as an attribute of properties, as shown in the example above.

Unpacking options

Artifact name

The name of the file/folder fetched by artifact-deployer can be customised; by default it is the name of the JSON key (i.e my-amp), but you can override it using destinationName attribute:

"artifacts": {
    "my-amp": {
    "enabled": true,
    "path": "my-amp/target/my-amp.amp",
    "destinationName" : "my.amp"
    "destination": "/var/lib/tomcat7/amps",
    "owner": "tomcat7"

Including a single sub-folder

You can only include one specific subfolder of a ZIP, using the following syntax:

"artifacts": {
  "keystore": {
    "enabled": true,
    "groupId" : "org.alfresco",
    "artifactId" : "alfresco-repository",
    "version" : "5.0.a",
    "destination": "/var/lib/tomcat7/keystore",
    "subfolder": "alfresco/keystore/\*",
    "owner": "tomcat7"

Unit testing

bundle update
bundle exec rake

Integration testing

kitchen test

Dependent cookbooks

python >= 0.0.0
file >= 0.0.0
maven >= 0.0.0

Contingent cookbooks

There are no cookbooks that are contingent upon this one.

Foodcritic Metric

0.8.2 failed this metric

FC031: Cookbook without metadata file: /tmp/cook/7baa6b3258b6ee92d208e630/artifact-deployer/metadata.rb:1
FC045: Consider setting cookbook name in metadata: /tmp/cook/7baa6b3258b6ee92d208e630/artifact-deployer/metadata.rb:1