Skip to content
This repository has been archived by the owner on Jan 23, 2019. It is now read-only.

Use 'use_inline_resources' to ensure notifications propagate correctly #89

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

wlonkly
Copy link

@wlonkly wlonkly commented Jun 27, 2017

PR #69 updated the monit provider to use run_action on the provided resources to make external notifications propagate (i.e., so that a 'notifies' in a monit_monitrc's block would run). But that has the side effect of not firing the 'notifies' inside the monit_monitrc resource, and thus monit never reloads when a new monit_monitrc resource is created.

This uses use_inline_resources to evaluate the monit template in its own context, so that that context will fire notifications declared on the monit_monitrc resource, while still firing the notification on the template itself.

Tested against Chef 12.14.68, 12.21.1 (current) , 13.1.31 (current).

PR phlipper#69 updated the monit provider to use run_action on the provided
resources to make external notifications propagate (i.e., so that a
'notifies' in a monit_monitrc's block would run). But that has the side
effect of not firing the 'notifies' inside the monit_monitrc resource,
and thus monit never reloads when a new monit_monitrc resource is
created.

This use use_inline_resources to evaluate the monit template in its own
context, so that that context will fire notifications declared on the
monit_monitrc resource, while still firing the notification on the
template itself.

See notes on updated_by_last_action here:
  https://docs.chef.io/custom_resources_notes.html
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant