16413 - Missing default discovery (mc) in mcollecitve 2.2 debian

In the past the discovery plugins were not included in the
debian mcollective-common install file.

The discovery directory has been added to the mcollective-common
install file.
16413 - Missing default discovery (mc) in mcollecitve 2.2 debian

changelog and revision update
16410 - summary() aggregate function should support boolean values

In the past the Summary aggregate plugin would fail when trying to
format the output for a non string response value.

Non string response values are now turned into strings before
formatting.
16410 - summary() aggregate function should support boolean values

Update changelog
16503 - Bignum should be an accepted data type for Result values

Allow Bignum values to be stored in Result
16503 - Bignum should be an accepted data type for Result values

add tests and update changelogs
16569 - Timeout from DDL does not propagate when using direct discovery

Each Message object has options, filters, timeouts and such.  The client
should use the options in the Message object when ever it gets asked to
publish a request - else take what comes in as an arg or already there.

As the RPC framework is now completely based on the Message object we
did not set it in the constructor of the RPC client rather relying on
the per message behavior as that will be less prone to failure

Ideally we should completely revisit how the client class handles
options but this does improves things in general - the stats method
will be correct in all cases for the most recent message where
previously there was a small race

maint: fix a test that fails with --order random
16424 - data plugin ddls should allow queryless plugins

The data query language lets you do things like:

   -S "puppet().enabled = true"

ie. a data query that takes no input, unfortunately the DDL required
all data plugin DDLs to declare a input called :query which in this case
would have no meaning and force users to write input blocks in the DDLs
just to satisfy the validation and no other reason.

This requirement is now being relaxed
maint: fix logging level in M::Client
16617 - validation errors should show the key that is failing

Previously the error shown during validation did not indicate what input
were failing which made debugging things harder.  We now show the input
key name
16411 - for actions with multiple aggregate defined failure in one should not prevent others from returning data

Previously if a invalid summary field was defined in a ddl no summary
results would be displayed.

Valid summaries will now always be displayed, even if invalid ones
have been defined in the ddl.
16415 - supplying formats for aggregate functions does not work

In the past passing a format argument to an aggregate function in
the ddl did not change the output format.

Passing a format argument to an aggregate function will now correctly
format the output.
16415 - supplying formats for aggregate functions does not work

Update changelog
16735 - aggregate formatting should be done as part of output not as part of the plugins

In the past aggregate summary plugins had to take care prepending spaces
to output lines.

Prepending display output with whitespaces has now been moved to the
stats class.
16735 - aggregate formatting should be done as part of output not as part of the plugins

Update changelog
16411 - for actions with multiple aggregate defined failure in one should not prevent others from returning data

maint: fix wrong commit
16735 - aggregate formatting should be done as part of output not as part of the plugins

maint: fix missing commits caused by #16411
16965 - Release 2.2.1

Update changelog, release notes and Rakefile
17138 - rpcutil#get_data always pass input to the data plugins even when none is expected

Previously all data plugins required an input even those that would not
logically do anything with that input.

Data plugins should though be able to have no input and this bug was
fixed in 2.2.1 but unfortunately the rpcutil#get_data action would in
the case of no input turn the nil into "" which means get_data could not
be used to retrieve data from such plugins.

This fixes that short coming, also removes some unneeded input
validation that is now handled by the DDL before invoking the agent
17137 - data plugins without input fails to show any help

The data help template assumed a query was set in the DDL, now that
queries are optional that failed and the templates refused to render.

Now showing a nice message in those cases