-
Notifications
You must be signed in to change notification settings - Fork 290
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Request: Support for disabling the TCP/UDP Socket entirely #902
Comments
|
So setting client_bind and client_port to undef does not work, instead the socket_config should be missing entirely, is that correct? |
|
So, when I wrote https://github.com/sensu/sensu/pull/1800/files, I matched how the {
"client": {
"http_socket": {
"enabled": false
}
}
}to totally disable it, so for the TCP/UDP socket it's: {
"client": {
"socket": {
"enabled": false
}
}
}let me know if that helps! |
(GH-902) Add client_socket_enabled boolean parameter
|
Released in v2.53.0 |
New in Sensu 1.3.0 is the ability to disable the TCP/UDP socket entirely: https://github.com/sensu/sensu/blob/master/CHANGELOG.md#130---2018-03-09
Currently, it looks like this module, hard codes configuring the TCP/UDP socket here: https://github.com/sensu/sensu-puppet/blob/master/manifests/client.pp#L102-L105
Ideally, it'd be setup similar to the
http_socketallowing it to be completely disabled.The text was updated successfully, but these errors were encountered: