No description
Find a file
Ryan Coleman 2c82464f24 Adjust ownership to Puppet Labs
Prior to this commit, Inkling Systems was responsible for improving
and maintaining this module. The maintainer has moved on and Inkling
wished for Puppet Labs to continue with this modules maintenance.

This commit adjusts the README and Modulefile for this change in
ownership.
2012-10-24 10:20:20 -07:00
lib Bring database, database_user, and database_grant into alignment with mysql module 2012-06-08 22:30:27 -07:00
manifests Merge pull request #17 from puppetlabs-operations/master 2012-10-18 04:19:37 -07:00
spec Update Vagrant tests to be compatible with new structure 2012-07-29 13:35:39 -07:00
templates Try to make the pg_hba.conf work on postgres 8.1 2012-07-19 18:02:12 -07:00
tests Add postgresql::db convenience type, improve security 2012-06-09 09:23:11 -07: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 Adjust ownership to Puppet Labs 2012-10-24 10:20:20 -07:00
README.md Adjust ownership to Puppet Labs 2012-10-24 10:20:20 -07: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::user (just for clarity; users are roles in postgres)
  • postgresql::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'           => '*',
        'manage_redhat_firewall'     => true,
        'postgres_password'          => 'TPSrep0rt!',
    },
}

Manage users / roles and permissions:

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

postgresql::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.