Forge Home


Installs Artifactory Pro. Not HA configuration.


4,273 latest version

5.0 quality score

We run a couple of automated
scans to help you access a
module's quality. Each module is
given a score based on how well
the author has formatted their
code and documentation and
modules are also checked for
malware using VirusTotal.

Please note, the information below
is for guidance only and neither of
these methods should be considered
an endorsement by Puppet.

Version information

  • 2.1.0 (latest)
released Jun 28th 2019
This version is compatible with:
  • Puppet Enterprise 2018.1.x, 2017.3.x, 2017.2.x, 2017.1.x, 2016.5.x, 2016.4.x
  • Puppet >= 4.7.0 < 6.0.0
  • , ,

Start using this module

  • r10k or Code Manager
  • Bolt
  • Manual installation
  • Direct download

Add this module to your Puppetfile:

mod 'fervid-artifactory_pro', '2.1.0'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add fervid-artifactory_pro
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install fervid-artifactory_pro --version 2.1.0

Direct download is not typically how you would use a Puppet module to manage your infrastructure, but you may want to download the module in order to inspect the code.



fervid/artifactory_pro — version 2.1.0 Jun 28th 2019

Build Status Puppet Forge Puppet Forge

Table of Contents

  1. Overview
  2. Module Description - What the module does and why it is useful
  3. Setup - The basics of getting started with artifactory
  4. Usage - Configuration options and additional functionality
  5. Reference - An under-the-hood peek at what the module is doing and how
  6. Limitations - OS compatibility, etc.
  7. Development - Guide for contributing to the module


This ONLY install Artifactory Pro.

If you are looking for the commercial installation look at:

Artifactory OSS:

Artifactory HA:

Github and gitlab are great for storing source control, but bad at storing installers and compiled packages.

This is where Artifactory comes in. It stores all of your organizations artifacts in an organized and secure manner.

Module Description

The Artifactory Pro module installs, configures, and manages the Artifactory pro binary repository.

The Artifactory Pro module manages both the installation and database configuration of Artifactory Pro.


Beginning with artifactory

Artifactory pro requires at a minimum a license key

class { '::artifactory_pro':
  license_key                    => 'abc123',

If you need to add database connectivity instantiate with the required parameters:

class { '::artifactory_pro':
  license_key                    => 'abc123',
  jdbc_driver_url                => 'puppet://modules/my_module/mysql.jar',
  db_type                        => 'oracle',
  db_url                         => '',
  db_username                    => 'my_username',
  db_password                    => 'efw23gn2j3',
  binary_provider_type           => 'filesystem',
  pool_max_active                => 100,
  pool_max_idle                  => 10,
  binary_provider_cache_maxSize  => $binary_provider_cache_maxSize,
  binary_provider_filesystem_dir => '/var/opt/jfrog/artifactory/data/filestore',
  binary_provider_cache_dir      => '/var/opt/jfrog/artifactory/',


All interaction for the server is done via ::artifactory_pro.



Public classes

Private classes

  • artifactory_pro::config: Configures Artifactory Pro.
  • artifactory_pro::post_config: Does pro post configuration.


Public defines

  • artifactory_pro::plugin: Adds a groovy plugin to the server




Sets the name of the Artifactory license key'.

This is required.


Sets the name of the yum repository. Defaults to 'bintray-jfrog-artifactory-pro-rpms'.

This can be changed if Artifactory needs to be setup from a different repository. Typically this is done if an organization has a 'trusted' yum repo.


Sets the base url of the yum repository to name. Defaults to ''.

This can be changed if Artifactory needs to be setup from a different repository. Typically this is done if an organization has a 'trusted' yum repo.


Sets the package name to install. Defaults to 'jfrog-artifactory-pro'.

This can be changed if Artifactory needs to install a differently named package. Possibly needed if na organization creates their own Artifactory package.


Tells the module whether or not to manage the java class. This defaults to true. Usually this is what you want.

If your organization actively manages the java installs across your environment set this to false.


Sets the location for the jdbc driver. Uses the wget module to retrieve the driver.

This is required if using a new data source.


Only required for database configuration. The type of database to configure for. Valid values are 'mssql', 'mysql', 'oracle', 'postgresql'.


Only required for database configuration. The url of the database.


Only required for database configuration. The username for the database account.


Only required for database configuration. The password for the database account.


Optional setting for the binary storage provider. The type of database to configure for. Valid values are 'filesystem', 'fullDb', 'cachedFS', 'S3'. Defaults to 'filesystem'.

filesystem (default)

This means that metadata is stored in the database, but binaries are stored in the file system. The default location is under $ARTIFACTORY_HOME/data/filestore however this can be modified.


All the metadata and the binaries are stored as BLOBs in the database.


Works the same way as filesystem but also has a binary LRU (Least Recently Used) cache for upload/download requests. Improves performance of instances with high IOPS (I/O Operations) or slow NFS access.


This is the setting used for S3 Object Storage.


Optional setting for the maximum number of pooled database connections. Defaults to 100.


Optional setting for the maximum number of pooled idle database connections Defaults to 10.


Optional setting for the maximum cache size. This value specifies the maximum cache size (in bytes) to allocate on the system for caching BLOBs.


Optional setting for the artifactory filestore location. The binary.provider.type is set to filesystem this value specifies the location of the binaries. Defaults to '$ARTIFACTORY_HOME/data/filestore'.


Optional setting for the location of the cache. This should be set to your $ARTIFACTORY_HOME directory directly (not on the NFS).



The url to the location of the groovy file.


This module has been tested on:

  • RedHat Enterprise Linux 5, 6, 7
  • CentOS 5, 6, 7


Since your module is awesome, other users will want to play with it. Let them know what the ground rules for contributing are.


This module is based on work by Fervid. The following contributors have contributed to this module:

  • Bryan Belanger
  • Paul Talbot