Add "friendly_name" to all Razor::Data classes

This adds a method to all Razor::Data classes to return a friendly name for
the type.  This can be used to talk about the object in, for example, error
messages elsewhere.

Signed-off-by: Daniel Pittman <daniel@rimspace.net>
Improve reporting of validation errors

This extends the validation framework to pass the context of the current
attribute through the system, and report using it.  This means that we will
see messages like "broker.name must refer to an ..." rather than "name must
refer to an ..." emitted.

That should help much more effectively understand where the problem was
located, rather than guessing at one of the many identically named attributes
it could possibly match.

https://tickets.puppetlabs.com/browse/RAZOR-191

Signed-off-by: Daniel Pittman <daniel@rimspace.net>
Implement a 'size' validation check for attributes

This implement a check to validate the size of an attribute; it only makes
sense for string, object/map, and array types.  It uses a range to verify the
minimum and maximum size of the object in characters, or contained entities.

This, in turn, supports verification that inappropriate length entities are
not passed in our data.

Signed-off-by: Daniel Pittman <daniel@rimspace.net>
Apply a size check to tag names, rejecting zero-length names

This applies the size validation check to tag names, to ensure that they are a
legal length matching our definition in the database.  That is, between one
and infinity characters long.

https://tickets.puppetlabs.com/browse/RAZOR-137
Signed-off-by: Daniel Pittman <daniel@rimspace.net>
Apply size checks to all other commands, where relevant

This commit whips through all the other commands and applies a size check to
string arguments -- matching our database constraints.  This kind of shows how
incoherent those constraints are, varying wildly between infinite and
constrained, but they are our current constraints.

Signed-off-by: Daniel Pittman <daniel@rimspace.net>
Add user help to all commands

This adds user-facing help to all commands, based on the existing
documentation.  This will be automatically exposed to the client through the
new command metadata API, and will permit this information to be shared with
the client automatically -- as well as future updates to help about the
commands as we improve the software.

Signed-off-by: Daniel Pittman <daniel@rimspace.net>
Detect and report out-of-sync migrations via the API

When the Razor code and database migrations are out of sync, significant
problems can occur.  This adds code to detect when this situation has shown
up, report it, and refuse service to all callers.

For the client this will result in an error message to the user, including
instructions on how to fix the problem.

For MK images, etc, it will result in an error that they will observe and
retry in the near future; this is the best we can do, since we can't be sure
that the changes have not altered the behaviour they should undertake.

https://tickets.puppetlabs.com/browse/RAZOR-158
Signed-off-by: Daniel Pittman <daniel@rimspace.net>
Add `locales` data and template to packages

The locales directory will be shipped, with both the PO file template, and any
PO files that we have included that support translations.  This supports our
translation efforts.

Signed-off-by: Daniel Pittman <daniel@rimspace.net>
Fixing `create-repo` documentation
(RAZOR-190) Add command to set repo source

Add an set-repo-source command that will allow the user to set the source of an existing repo. The user can also supply a 'refresh' option that can be true or false (defaults to true) that will force the repo to refresh its content from the new source.  This is required, because if you create the repo and then policies/tags etc only to realise you botched the definition of the repo, you first have to pull down all the dependants (policies and the like) to delete/recreate the repo.