-
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
transport.json not created when transport_type = rabbitmq #809
Labels
Comments
|
@htallur what's the expected behaviour? I suppose that a transport.json has to be created in any case , both with redis and rabbitmq transport . I can eventually add a parameter $ensure to the sensu::transport class, to allow users to eventually force the removal of transport.json |
alvagante
added a commit
to alvagante/sensu-puppet
that referenced
this issue
Sep 5, 2017
4 tasks
alvagante
added a commit
to alvagante/sensu-puppet
that referenced
this issue
Oct 23, 2017
alvagante
added a commit
to alvagante/sensu-puppet
that referenced
this issue
Oct 23, 2017
…bbitmq Fix for sensu#809 Added spec test
ghoneycutt
added a commit
that referenced
this issue
Oct 23, 2017
|
Released in v2.37.0 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description of problem
transport.json is not created
incorrect logic in transport.pp
if $::sensu::transport_type != 'redis' {
$ensure = 'absent'
} else {
$ensure = 'present'
}
ensure = 'absent', when transport_type = 'redis' in transport.pp
The text was updated successfully, but these errors were encountered: