Cosmetic fixes to parse-config method
Don't alias resources with composite namevars

Normally, as part of converting a catalog to the PuppetDB wire format,
we ensure that every resource has its namevar as one of its aliases.
This allows us to handle edges that refer to said resource using its
namevar instead of its title.

However, Puppet implements `#namevar` for resources with composite
namevars in a strange way, only returning part of the composite name.
This can result in bugs in the generated catalog, where we may have 2
resources with the same alias (because `#namevar` returns the same thing
for both of them).

Because resources with composite namevars can't be referred to by
anything other than their title when declaring relationships, there's no
real point to adding their aliases in anyways. That neatly side-steps
the problem.

Signed-off-by: Deepak Giridharagopal <deepak@puppetlabs.com>
(#15281) Postgres support in acceptance tests

This commit adds rudimentary postgres support in acceptance tests.

Known issues / concerns:

* It relies on this pull req for the acceptance framework:

https://github.com/puppetlabs/puppet-acceptance/pull/258

* It is using puppet modules for a lot of this, and some of the
modules have not been polished / released yet, so it's checking
them out from pretty stupid locations on github.

* It's not configurable; it makes the acceptance tests ALWAYS run
on postgres; we might want to figure out how to make it possible
to toggle between postgres and the embedded db.
(#15378) Improve behavior of acceptance tests in single-node environment

We have some acceptance tests that require multiple nodes in order
to execute successfully (mostly around exporting / collecting
resources).  If you tried to run them in a single-node environment,
they would give a weird ruby error about 'nil' not defining a certain
method.

This commit simply modifies those tests so that they will be skipped
if you are running without more than one host.
(#15281) Add ability to toggle between database backends

This commit allows the acceptance tests to be configured
to use either the embedded database OR postgres.  It
introduces some "options files" (which rely on pull req
number 259 on the acceptance framework)--these are used
to provide default values for various options that
we would normally specify from the command line; they
are also used to introduce the "puppetdb_database" option,
which is what we will use to toggle between the different
database backends.
Merge pull request #214 from cprice-puppet/refactor/master/verify-config-path

Cosmetic fixes to parse-config method
(#14606) Add curl-based query examples to docs
Merge pull request #221 from cprice-puppet/maint/master/14606-add-curl-examples-to-docs

(#14606) Add curl-based query examples to docs
(#15281) print out database.ini so that it will be in the log
Merge pull request #219 from cprice-puppet/feature/master/15281-postgres-acceptance-tests

(#15281) Postgres support in acceptance tests
Merge pull request #220 from cprice-puppet/maint/master/15378-single-node-acceptance

(#15378) Improve behavior of acceptance tests in single-node environment
Document how to configure PuppetDB with puppet apply

This covers how to configure routes.yaml to disable the inventory
service, as well as the need for an SSL proxy in the case where there is
no master.
Merge pull request #222 from nicklewis/document-puppet-apply

Document how to configure PuppetDB with puppet apply
Merge pull request #217 from grimradical/composite-namevar-support

Don't alias resources with composite namevars
Add release ENV var to puppetdb packaging

This commit modifies the packaging of puppetdb
to allow the user to specify a tag release, e.g.
0.9.2-1puppetlabs2 vs 0.9.2-1puppetlabs1.

Signed-off-by: Moses Mendoza <moses@puppetlabs.com>
Merge pull request #223 from MosesMendoza/maint/master/add_release_option_to_puppetdb_packaging

Add release ENV var to puppetdb packaging
Add SRPMS directory creation to rake:SRPM task

Some configurations of rpmbuild won't make the SRPMS directory automatically
when building an RPM, so this commit adds a mkdir_p to the rake task to make
the directory before running rpmbuild. Otherwise, the rpmbuild call fails when
rpmbuild can't write the src rpm to the SRPMS directory (because it doesn't
exist).
Merge pull request #224 from haus/add_srpm_dir_creation_to_rake_task

Add SRPMS directory creation to rake:SRPM task
Fix resource terminus specs to pass against Puppet master branch
Add a `rake version` task to print the version

This is useful for CI, where we need to determine what version of the
code is being tested, for building packages, etc.