packagecloud

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 packagecloud
   • What packagecloud affects
   • Setup requirements
   • Beginning with packagecloud
4. Usage - Configuration options and additional functionality
5. Limitations - OS compatibility, etc.
6. Development - Guide for contributing to the module

Overview

This is the packagecloud.io puppet module which allows you to easily get public and private packagecloud.io repositories installed on your infrastructure.

Module Description

This is the packagecloud.io puppet module which allows you to easily get public and private packagecloud.io repositories installed on your infrastructure.

Setup

What packagecloud affects

• The packagecloud module will:
  • install apt-transport-https or pygpgme as appropriate for the underlying system
  • add the packagecloud.io gpg key for verifying repository metadata
  • add apt or yum repos to the system by creating the necessary files under /etc/apt/sources.list.d/ and /etc/yum.repos.d/, respectively

Beginning with packagecloud

Simply install the packagecloud puppet module and you will be able to use the packagecloud::repo resource in your manifests:

packagecloud::repo { 'username/publicrepo':
  type => 'rpm',
}

packagecloud::repo { 'username/privaterepo':
  type => 'deb',
  master_token => 'eae123bca276162f376b9614ba134fa7993624a8de0bb3a2',
}

packagecloud: enterprise users can specify the host and port by setting server_address:

packagecloud::repo { 'username/privaterepo':
  type => 'deb',
  master_token => 'eae123bca276162f376b9614ba134fa7993624a8de0bb3a2',
  server_address => 'http://my.internal.server.domain:1234/',
}

If you need to install more than one type of package from the same repository (for example, gem and deb files from username/publicrepo) you can use the fq_name parameter:

packagecloud::repo { 'deb repository for blah':
  fq_name => "username/blah",
  type => 'rpm',
}

packagecloud::repo { 'gem repository for blah':
  fq_name => "username/blah",
  type => 'gem',
}

In order to properly use Gem repos, be sure to set your Exec path to include the directory where your gem binary is located. For example, in your site.pp:

Exec {
  path => [ "/bin/", "/sbin/" , "/usr/bin/", "/usr/sbin/" ]
}

Usage

As in the examples show in the above section, you should specify at least type (which can be either deb, rpm, or gem) and optionally master_token if the repository is private.

Limitations

Currently supports the following operating systems:

• Redhat Enterprise Linux 5 and 6
• CentOS 5 and 6
• Scientific Linux 5 and 6
• Fedora 14 - 20
• AWS Linux
• Ubuntu 4.10 - 14.04
• Debian 4.0 - 8.0

Development

Pull requests are welcome!

Release Notes/Contributors/Etc

Special thanks to Eric Lindvall for help with puppet.