No description
Find a file
Chris Price 18167c7a3e Merge platform.pp back into params.pp
Nan showed me a trick that will let us keep all of that param stuff
inside of params.pp, make it a parameterized class, and still support
the ability for users to specify a custom (non-system-default) pg
version.  This commit takes the first step towards that pattern by
consolidating platform.pp and params.pp.  (Everything old is new again!)
2012-12-04 14:12:34 -08:00
lib Initial working implementation of ruby psql type/provider 2012-11-04 21:47:49 -08:00
manifests Merge platform.pp back into params.pp 2012-12-04 14:12:34 -08:00
spec Merge platform.pp back into params.pp 2012-12-04 14:12:34 -08:00
templates ACLs functioning, added examples in README and test, comments in config manifests 2012-10-22 12:34:24 -07:00
tests Re-add support for managing yumrepo 2012-12-02 23:06:36 -08:00
.gitignore Ignore output of puppet-module 2012-05-02 08:36:36 -07:00
CHANGELOG.md Advance version to 0.3.0 2012-09-17 10:42:05 -07:00
LICENSE Initial commit 2012-04-19 15:37:18 -07:00
Modulefile Stupid Librarian 2012-12-02 20:49:47 -08:00
Rakefile Pulled repository stuff out of params. 2012-12-02 20:49:47 -08:00
README.md Merge branch 'master' into cprice-puppet-feature/master/port-psql-to-ruby 2012-11-30 15:49:07 -08:00

Transferred from Inkling

This Puppet module was originally authored by Inkling Systems. The maintainer preferred that Puppet Labs take ownership of the module for future improvement and maintenance as Puppet Labs is using it in the PuppetDB module. Existing pull requests and issues were transferred over, please fork and continue to contribute here instead of Inkling. Previously: https://github.com/inkling/puppet-postgresql

Puppet module for PostgreSQL resources

This module provides the following defined resource types for managing postgres:

  • postgresql::initdb
  • postgresql::db
  • postgresql::role
  • postgresql::database_user (just for clarity; users are roles in postgres)
  • postgresql::database_grant

And the fallback, analogous to exec resources, only for SQL statements:

  • postgresql_psql

Basic usage

Manage a PostgreSQL server with sane defaults (login via sudo -u postgres psql):

include postgresql::server

...or a custom configuration:

class { 'postgresql::server':
    config_hash => {
        'ip_mask_deny_postgres_user' => '0.0.0.0/32',
        'ip_mask_allow_all_users'    => '0.0.0.0/0',
        'listen_addresses'           => '*',
        'ipv4acls'                   => ['hostssl all johndoe 192.168.0.0/24 cert'],
        'manage_redhat_firewall'     => true,
        'postgres_password'          => 'TPSrep0rt!',
    },
}

Manage users / roles and permissions:

postgresql::database_user{'marmot':
    password => 'foo',
}

postgresql::database_grant{'grant select to marmot':
   grantee   => 'marmot',
   on_object => 'my_table',
   perm      => 'select',
   require   => Postgresql::User['marmot'],
}

etc, etc.

Automated testing

Install and setup an RVM with vagrant, sahara, and rspec

$ curl -L get.rvm.io | bash -s stable
$ rvm install 1.9.3
$ rvm use --create 1.9.3@puppet-postgresql
$ gem install vagrant sahara rspec

Run the tests like so:

$ (cd spec; vagrant up)
$ rspec -f -d -c

The test suite will snapshot the VM and rollback between each test.

Next, take a look at the manifests used for the automated tests.

spec/
    manifests/
        test_*.pp

Contributors

Copyright 2012 Inkling Systems, Inc.

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.