The README isn't complete and neither are the installer hints, but this
starts to give a hit as to how everything is supposed to be put together.

This will allow more control over the management of PE and more
cleanliness of customer code.

To document which other modules are required

Enough to spark curiousity, if not enough to actually lay out how it
works

Without this, the PuppetDB Database host would not be correctly used.

There are default groups, and so name conventions, that should be
preserved in order to avoid conflicting with PE upgrades.

This reflects the specific architecture this module is designed to
deploy.

This is for pcp-broker, to help ensure long-lived connections stay
alive.

Because in PE, it defaults to using a first-letter capitol

To better accommodate upcoming tooling that deploys changes to a selected
environment group. The name "All Environments" better communicates what
nodes will be in to the group.

To allow templatized files to be created and uploaded using tasks

Incremental changes

To return simply a node's hostname

Because if there are undef values in the all hosts array, it's not a
valid target

So it sticks around for a minute. The working directory for tasks is
cleaned up as soon as the task finishes.

Use --transient instead of --static because that seems to be closer to
what Puppet cares about and will use for certname

Because the installer can't sign certs that have auth extensions

We expect it to fail, really

To prevent stdin from being passed to these tasks when invoked. That can
tickle interesting bugs when things are being passed with --run-as and
--tty.

By short-circuiting PuppetDB's startup time.

Goes faster for testing