avoid Array#find in Puppet::Resource::Catalog::Puppetdb#find_resource
Fix README links to experimental APIs
Fix #clear_database helper path for embedded

Previously we were clearing the wrong path, this patch corrects that.

Signed-off-by: Ken Barber <ken@bob.sh>
Merge pull request #510 from kbarber/clear_database_embedded_bug

Fix #clear_database helper path for embedded
Update changelog for 1.3
Update docs version numbers to 1.3
Update event docs to include `certname` field
Merge pull request #511 from cprice-puppet/maint/master/prep-for-1.3-release

Maint/master/prep for 1.3 release
Merge pull request #508 from sodabrew/patch-1

Fix README links to experimental APIs
(#19884) Intermittent SSL handshake error

Certain versions of the JDK (1.7u6 and newer) appear to have a bug when
handling Diffie-Hellman exchange during SSL handshaking with OpenSSL
clients. Bug is discussed here:

https://forums.oracle.com/forums/thread.jspa?messageID=10999587

In me tests just having openssl's s_client connect to PuppetDB
repeatedly in a tight loop, we see the handshake error about 0.4% of the
time. So it's not a pervasive problem, but it's certainly annoying and
something users have seen and complained about somewhat regularly.

There are a few options available for fixing the problem:

1) Wait for Oracle to fix the problem. This is, of course, suboptimal.

2) Use BouncyCastle JSSE providers instead. This is workable, but in my
research would require changes to the JDK system policy files, which is
a huge PITA. There's also some concern about performance, if the BC
providers are markedly slower than the JSSE ones.

3) Disable the DHE ciphers.

This patchset implements option #3. The non-DHE cipher suites work fine,
support SSL and TLS, and are on the NIST and FIPS approved list. So...it
sucks that we need to disable the DHE cipher suites, but in an insane
world it's the sanest choice.

I've added a new option to the [jetty] section of the configuration file
called `cipher-suites`. It allows users, should they have the need, to
override the list of cipher suites used to one of their choosing.
(packaging) Remove pl-fedora-16 mock target. f16 is EOL
Merge pull request #513 from haus/remove_f16

(packaging) Remove pl-fedora-16 mock target. f16 is EOL
Only restrict the cipher suites on affected JVMs
Tweak docs for cipher-suites option
Docs: Update references to 1.2 to 1.3
Merge pull request #512 from grimradical/cipherz

(#19884) Intermittent SSL handshake error
Merge pull request #514 from nfagerlund/one_two_one_three

Docs: Update references to 1.2 to 1.3
Remove parallelization during export

In previous commits, we attempted to limit resource consumption
by using a "bounded" pmap when parallelizing our data exports.
This works great for preventing pmap from executing too many
operations simultaneously, but it does not prevent pmap from
building up a large backlog of work in the seq that it is
constructing; therefore, if the consumer of the seq is not
processing the work quickly enough, we can still end up using
a ton of memory.

The long-term solution for this is going to be to use a
`BlockingQueue` to prevent the pmap from generating work too
quickly.  However, the implementation of that can be a bit
tricky so for now we're opting for stability over performance.

This commit simply removes the parallelization and handles the
export serially.

In the future what I'd like to do is to polish up the
producer/consumer library that I wrote for this, and then use
that to solve the problem on both the import and export sides.
Don't check for newer available versions in dashboard for PE

Prior to this commit, the PuppetDB dashboard was checking for
newer versions of PuppetDB even if we are running inside of
a PE environment; this commit simply prevents the code
from checking for newer versions when we're in PE, and always
tells the dashboard that there are no newer versions available.
Merge pull request #516 from cprice-puppet/maint/master/no-parallelization-during-export

Remove parallelization during export