serverside cookbooks should be suggested but not required

[smcavallo]

Signed-off-by: S.Cavallo [email protected]
Addresses #616

Description

since this cookbook gets applied to both sensu server components (server + api + rabbitmq + redis) and sensu clients, the cookbooks which the server components require should be opted into.

Motivation and Context

allows consumers to opt-in for rabbitmq + redis cookbooks. opting in means that they'll be required to maintain these cookbooks as part of their chef implementation.

How Has This Been Tested?

normal testing as part of the PR process

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• [X ] Breaking change (fix or feature that would cause existing functionality to change)

This is a breaking change. Since the default is now opt-out, consumers would need to implement the dependency requirements in their wrapper cookbooks.

Checklist:

• [ X] My change requires a change to the documentation.
• [X ] I have updated the documentation accordingly.
• [ ]X I have read the CONTRIBUTING document.

[tas50]

I highly recommend not doing this as suggests does nothing on the client side of depsolving. If you want to make something not actually a dep you should just remove it and note that you need it in the readme (which is also bad so don't do that)

[smcavallo]

@tas50 - agreed - closing