Forge Home

Modules

Puppet

Resources

PuppetEcosystemPuppet CommunityUpdates

p4api

Manages the Perforce API installation on a node
Project URLRSS FeedReport issues

9,181 downloads

8,248 latest version

4.3 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.

Support the Puppet Community by contributing to this module

You are welcome to contribute to this module by suggesting new features, currency updates, or fixes. Every contribution is valuable to help ensure that the module remains compatible with the latest Puppet versions and continues to meet community needs. Complete the following steps:

  1. Review the module’s contribution guidelines and any licenses. Ensure that your planned contribution aligns with the author’s standards and any legal requirements.
  2. Fork the repository on GitHub, make changes on a branch of your fork, and submit a pull request. The pull request must clearly document your proposed change.

For questions about updating the module, contact the module’s author.

Version information

  • 0.1.2 (latest)
  • 0.1.1
  • 0.1.0
released Jan 25th 2016
This version is compatible with:
  • Puppet Enterprise >= 3.0.0 < 2015.4.0
  • Puppet >= 3.0.0 < 5.0.0
  • , , ,

Start using this module

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

Add this module to your Puppetfile:

mod 'alanpetersen-p4api', '0.1.2'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add alanpetersen-p4api
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install alanpetersen-p4api --version 0.1.2

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.

Download

Documentation

alanpetersen/p4api — version 0.1.2 Jan 25th 2016

p4api

Overview

This module manages the Perforce API installation on Linux systems.

Usage

At a minimum, you can accept the defaults and simply use include p4api to manage the Perforce API on the node.

You can override defaults using hiera, or by specifying parameters when declaring the p4api class. For example:

class { 'p4api':
  version => '14.3',
  osuser  => 'perforce',
  osgroup => 'perforce',
}

Parameters

  • version - the P4API version you want to manage. This defaults to 15.2.
  • base_download_url - the base URL from which the P4API distribution will be downloaded. This defaults to ftp://ftp.perforce.com/perforce.
  • dist_dir - the distribution directory (under the r${version} directory) that will contain the distribution tarball. This is calculated in the params class.
  • base_perforce_dir - the base directory where the P4API (and symlink) will be created. This defaults to /opt/perforce.
  • manage_base_dir - a boolean indicating whether or not this module should attempt to manage the base directory. This defaults to true. You might want to set this to false, for example, if some other Perforce product (like GitFusion) is also being managed on the system.
  • create_symlink - a boolean indicating whether or not the symlink should be created. This defaults to true.
  • symlink_name - the name of the symlink that will point to the actual P4API distribution directory. This defaults to p4api.
  • osuser - the OS user account that will own the P4API directory and symlink. This defaults to root. This module will NOT manage the user... that should be done separately.
  • osgroup - the OS group that will own the P4API directory and symlink. This defaults to root. This module will NOT manage the group... that should be done separately.
  • staging_dir - the directory where the P4API distribution will be downloaded. This defaults to /var/staging. The distribution will be downloaded into the p4api subdirectory.

Limitations

Currently, the module only supports Linux. A Windows version is being considered.