This is necessary for the scenario when you push a new, broken monit
config out, and then set a state=reloaded handler - the error was
previously swallowed so you could end up with successful play but missing
monitoring (!).

Signed-off-by: Chris Lamb <chris@chris-lamb.co.uk>

Improve error messages.

between the restart/start command and the summary command.

Refactor to avoid repeating the status, and fail if a given call to monit fails.

Signed-off-by: Max Riveiro <kavu13@gmail.com>

* Adds another module utility file which generalizes the
  access of urls via the urllib* libraries.
* Adds a new spec generator for common arguments.
* Makes the user-agent string configurable.

Fixes #6211

* Adds another module utility file which generalizes the
  access of urls via the urllib* libraries.
* Adds a new spec generator for common arguments.
* Makes the user-agent string configurable.

Fixes #6211

If we do this, we risk outputting two JSON payloads, which will be
unparsable.

Errors everytime...

out there have same name.
Signed-off-by: Brian Coca <briancoca+dev@gmail.com>

event types for anything other than myapps here.

changed apikey and apiid to api_key and api_id and noted that it is boundary tags not ansible tags as per mpdehaan

Changed shebangs that use /usr/bin/env to use /usr/bin/python and therefore be compatible with the ansible_python_interpreter variable.