Skip to content
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

Add an example of custom resource using workaround for why-run #11

Closed
wants to merge 5 commits into from

Conversation

kamaradclimber
Copy link
Contributor

If custom_resource is defined with an explicity support for why-run,
choregraphie works correctly.

See chef/chef#4537

Some resources are already risky (reboot for instance), users
consequently want to protect against all instances of such resources
even though the list might not be clearly defined (or evolving).

Example:

    choregraphie 'my super service' do
      on /^reboot\[/

      before do
        downtime('myservice')
      end
    end

Also update the readme a bit.

Change-Id: I9b5b1f18cefb6bfc977aabc1179c19ffa51f4a84
Change-Id: Id501bbea4a3c87c2d2944b0d72e8d54119c59649
Change-Id: I6eb25d5d43dfb308ee86a60f06ff0de9b4e6c5ee
Change-Id: Id4fe6fb4b60c0b15be244406f20a93cdc2cec101
If custom_resource is defined with an explicity support for why-run,
choregraphie works correctly.

See chef/chef#4537

Change-Id: Ibcdb11135f2d7477584f1707ffd174ca1b7c56e7
@kamaradclimber
Copy link
Contributor Author

merged manually

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant