kindredgroup / puppet-go

Puppet module for managing Thoughtworks Go
Other
8 stars 12 forks source link

go

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 go
  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

Overview

The go module manages the life cycle of the continuous delivery platform Go provided by Thoughtworks. It aims for self containment and only focus on solving tasks surrounding the Go product with minimal external dependencies.

Module Description

Thoughtworks Go is a continuous delivery platform used for build, packaging and orchestrating application deployments. Go uses a server component for the administration, presentation and scheduling part, and an agent component responsible for carrying out the work. The Go module manages these concerns within separate named spaced classes.

Setup

Setup Requirements

Go depends on JDK to be installed in order to run. This dependency must be managed outside of the Go module. See: http://www.thoughtworks.com/products/docs/go/current/help/system_requirements.html

In addition, the Go module depends on functions and resource types provided by the puppetlabs-stdlib module and the puppetlabs-concat module.

Beginning with go

Server

class { '::go::server':
    manage_package_repo => true
}

Agent

class { '::go::agent':
    manage_package_repo => true
} ->
::go::agent::instance { 'agent1':
    path            => '/opt/go',
    go_server_host  => 'localhost',
    go_server_port  => 8153
}

Usage

The Go module exposes the following classes

It also exposes these defined types:

The exposed classes are contained using the anchor pattern provided via puppetlabs-stdlib, thus you should be able to form reliable dependencies on these classes as expect all of its resources to be realized.

Reference

See the code

Limitations

Tested and used on Redhat and Ubuntu. See metadata.json for supported OS combinations.

Development

$ bundle install
$ bundle exec rake validate
$ bundle exec rake spec