fix checkstyle
changed ContentResource#update to use contentId in the resource path
Merge pull request #80 from witlessbird/content-update-fix

changed ContentResource#update to use contentId in the resource path
Checkstyle fixes.
857918: Add quotes around the invalid service level
800145: Update pools across all owners on product import

Previously, upon importing an export file, if a product was modified,
we would regenerate the certificates of all entitlements that referenced
that product. We would then run a refreshPools on the owner that
imported the export. the refreshPools would adjust that owner's pools to
reflect the new product attributes, but not any other owners.

That was the intention, anyways. In reality, the code to look for
changed products compared the new forms of the products to the products
from the db, but only after it had already updated the db. Thus, the
products were never found to have changed, and no certs were
regenerated.

This patch fixes that up by comparing the new forms of the products with
the form as it is in the db, before storing the new form. Further, it
corrects the code to check for changes, catching more instances when the
products are different.

To refresh the pools referencing the affected products, but also ensure
that a pool that references two products, or a pool that is owned by the
importing owner is not refreshed multiple times, introduce a new
Refresher object that takes care of gathering up the objects we want to
trigger a refresh on (products, owners), then executes the pool
refreshes and entitlement regens without repeating anything.

The existing code to trigger a refresh by product was being overly broad
on what pools it would refresh (triggering for all pools for an owner
that had a single pool that referenced the product, rather than just the
referencing pools). This patch also narrows the focus down to just the
affected pools, and introduces a spec test to verify that.
Merge pull request #82 from candlepin/bkearney/857918

857918: Add quotes around the invalid service level
Merge pull request #83 from candlepin/jbowes/refresher

800145: Update pools across all owners on product import
Added candlepin.enable_cert_v3 config property.

This property will be used to determine if we should enable/disable
candlepins cert V3 functionality and fall back to old V1 certs.

Allowed spec tests to bypass the enable cert v3 config property.
The V3 spec tests were failing due to defaulting the
candlepin.enable_cert_v3 config property to false. Because there
was no way for a spec test to determine if V3 cert support was
disabled, a custom fact was added to test consumer so that the
config property could be overridden in our tests.

CP will check for that fact (system.testing) and if it exists,
CP will create certs as normal.

This should be removed once cert V3 support has been added elsewhere.
Merge pull request #81 from candlepin/mstead/disable-v3-via-config

mstead/disable v3 via config
857494: Add DB password to liquibase command.
Save the name of the import file uploaded in the event history
Merge pull request #84 from candlepin/wottop/US645

Save the name of the import file uploaded in the event history
863518: put unitOfWork.end() in a finally block

We're getting occurrences of unitOfWork.begin() being called before an end() is
called. The finally should fix this situation.
Update Zanata strings
Automatic commit of package [candlepin] release [0.7.13-1].
Allow updating consumer names

Support name as another field that can be updated on consumers via PUT.
When name is updated, we must regenerated the idcert, so that the new
name is included in the subject alt name.
adding internal koji repo
Add new mechanism for detecting/overriding import conflicts.

Added several new types of manifest import conflicts which can be
overridden by the caller. On import 409 responses will also include
progrematic keys which other projects can use to distinguish why the
import failed. The request can be retried with a multi-valued force
parameter to override.

force=true will behave as it did before, ignoring an older manifest
creation date and importing anyhow.

Added distributor conflicts which allow the caller to link their org to
a new upstream distributor. (should they have deleted it accidentally,
etc) This may cause drastic changes to their subscriptions, but not if
used for a new distributor in the same upstream org and using the same
pools.

Signature checking code is brought back but disabled until other
projects are ready for it.

We also now distinguish between an older manifest, and the same manifest
currently imported.
changing the internal name so it doesn't start with yum.

Not starting with yum makes building community builds easier. Since now you can
simply type: tito release --all-starting-with=yum

Today you have to do --all-starting-with=yum-f then again with
--all-starting-with=yum-r etc.  It's rather annoying. So removing the one item
that shouldn't be run externally makes more sense.