Pagerduty docs not in line with current behaviour

[wilb]

Historically, the Pagerduty integration used to "just work" when you used added the pagerduty recipe to your run list and set your API key as an attribute. I've got a box I provisioned a few years ago that is still using an old version of the cookbook that still behaves like this

Having just spun up a new host using the latest cookbook it appears that this behaviour has changed, but the documentation doesn't reflect this. The pagerduty user still gets created but no longer gets added to the admin users group by default (I assume this is now intentional). I've also created a nagios_pagerduty databag and specifically created a "pagerduty_crit" contact with "admin_contactgroup" set to true but this also didn't add that user to the admin contactgroup either...

Overriding the admin group via nagios_contractroups to manually add the pagerduty user replicates the old behaviour, but maybe the documentation should be updated to better reflect the current behaviour?

[wilb]

#288 seems to refer to the admin_contactgroup issue.

[damacus]

Any way you'd like to submit a PR for this issue?

Is so that'd be greeeeat.

[github-actions]

Marking stale due to inactivity. Remove stale label or comment or this will be closed in 7 days. Alternatively drop by the #sous-chefs channel on the Chef Community Slack and we'll be happy to help! Thanks, Sous-Chefs.