(GH-902) Add client_socket_enabled boolean parameter

[treydock]

Pull Request Checklist

Description

Add client_socket_enabled parameter that when false will disable the sensu client socket.

Related Issue

Fixes #902 .

Motivation and Context

This change is required to support sensu 1.3.0 to allow disabling the sensu client socket.

How Has This Been Tested?

Unit tests added

General

• Update README.md with any necessary configuration snippets

• New parameters are documented

• New parameters have tests

• Tests pass - bundle exec rake validate lint spec

[jaredledvina]

I just caught something in our environment w/ the Client TCP/UDP socket disabled, if you do disable it, but keep deregister_on_stop set to true, it fails because that setting is enabling this: https://github.com/sensu/sensu-build/blob/c227fc99b74cbcf52ec88fe9d1a12ab813b299d6/sensu_configs/init.d/sensu-service#L200-L204

There's also https://docs.sensu.io/sensu-core/1.3/reference/clients/#deregistration-attributes as an alternative to the way deregister_on_stop works which does work w/ the client socket disabled.

Just wanted to throw that out there.

[ghoneycutt]

@jaredledvina Can you please confirm this patch works for you before we merge?

[jaredledvina]

@ghoneycutt - Absolutely, I'll give it a run through today.

[jaredledvina]

Looks good, setting client_socket_enabled to false does disable the local client TCP/UDP socket.

[ghoneycutt]

Released in v2.53.0