Create a responders field from the users, teams, escalations, and
schedules values in Sensu. The teams value can be used as before and the
other three work the same way. The correct type key is added for you.
Because the old recipients value could contain any of the above, I
haven't tried to map it to the new values so this is a backwards
incompatible change as it won't use it any longer, however the teams
value still works as before.
Pull Request Checklist
Fixes #83
General
[x] Update Changelog following the conventions laid out here
[x] Update README with any necessary configuration snippets
[ ] Binstubs are created if needed
[x] RuboCop passes
[ ] Existing tests pass
New Plugins
[ ] Tests
[ ] Add the plugin to the README
[ ] Does it have a complete header as outlined here
Purpose
Known Compatibility Issues
The existing teams value is still used but the recipients value is no longer used. Instead users, escalations and schedules should be utilised.
Create a responders field from the users, teams, escalations, and schedules values in Sensu. The teams value can be used as before and the other three work the same way. The correct type key is added for you.
Because the old recipients value could contain any of the above, I haven't tried to map it to the new values so this is a backwards incompatible change as it won't use it any longer, however the teams value still works as before.
Pull Request Checklist
Fixes #83
General
[x] Update Changelog following the conventions laid out here
[x] Update README with any necessary configuration snippets
[ ] Binstubs are created if needed
[x] RuboCop passes
[ ] Existing tests pass
New Plugins
[ ] Tests
[ ] Add the plugin to the README
[ ] Does it have a complete header as outlined here
Purpose
Known Compatibility Issues
The existing teams value is still used but the recipients value is no longer used. Instead users, escalations and schedules should be utilised.