supervisor_service triggers an enable on every run

[jmound]

version 0.4.11:

supervisor_service "gunicorn" do
end

causes this:

- Enabling supervisor_service[gunicorn]

on every run, even in this base example where nothing has changed and the service is already enabled.

[jmound]

I thought this might be a fix, it's related, but not the same issue.

[levmichael3]

hi,
Any luck here around this issue?
Was it solved?

[jmound]

Not that I know of, but I haven't checked in a while, and there have been plenty of commits since then.

[levmichael3]

Thanks.
I am trying to extend this LWRP and provide a reread.

Sent from Blue Mail

On Jan 16, 2015, 18:39, at 18:39, "Justin M." [email protected] wrote:

Not solved, but I haven't checked in a while, and there have been
plenty of commits since then.

---

Reply to this email directly or view it on GitHub:
#62 (comment)

[jslusher]

• 1 on finding a fix for this. Thanks for the cookbook!

[levmichael3]

Have you forked this fix?

[borntyping]

Removing the duplicated execute[supervisorctl update] resources seems to fix this (i.e. replacing the execute resources generated by enable_service and disable_service with a single instance in the main recipe).