sonodar

if (process.argv.length < 3) {
  throw `Usage: ${process.argv[1]} path_prefix`
}
const PATH_PREFIX = process.argv[2]

const path = require('path')
const AWS = require('aws-sdk')
const ssm = new AWS.SSM()

function getParametersByPath(nextToken, callback) {

tnolet

NB: The following examples where done on Puppet Enterprise 3.0 running on Centos 6. Should be similar for open source versions, except for some file locations.

1. Logging into the PuppetDB PostgresQL database on Linux

The easiest way to snoop around in de actual PuppetDB postgres database is using the command prompt. You have to be the peadmin user though. Couldn't get it working just under root.

[root@master bin]# sudo su - pe-postgres -s /bin/bash
-bash-4.1$ /opt/puppet/bin/psql
psql (9.2.4)

Type "help" for help.

rodjek

#!/usr/bin/env ruby
	
require 'puppet'
require 'puppet/configurer'

Puppet.settings.parse
c = Puppet::Configurer.new
c.download_plugins
c.download_fact_plugins

josch

# Services to use:
# Choices: security updates (from security.debian.org), volatile updates (from volatile.debian.org)
apt-setup-udeb  apt-setup/services-select       multiselect     
# Non-existing physical volume
partman-auto-lvm        partman-auto-lvm/no_such_pv     error   
# Check the integrity of another CD-ROM?
d-i     cdrom-checker/nextcd    boolean false
# Install GRUB?
grub-installer  grub-installer/grub_not_mature_on_this_platform boolean false

ccaum

#!/usr/bin/env ruby

require 'rubygems'
require 'puppet'
require 'puppet/face'
require 'puppet/cloudpack'

options = { 
  :image   => 'ami-3d76b754',
  :type    => 'm1.large',