- From: Boris Shulman <
>
- To:
- Subject: [chef] Re: Re: triggering undeploy action
- Date: Mon, 23 Aug 2010 23:39:07 +0300
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=LQeKrKvs18UPXE2eX2rXKM8OViFphdL/8iFF919E0stHkQsOhFrCgbBxyNGA8YXGMf B7KUZz+R033uIn0ZWk6Hg13ODS4H3OZ481KHIQ2aRXtbKphQ7Q5V+6N1RIfpZ0ABrGdE BBKMWJxKLNMGzxgsg50I1Xlp/rvs8iEqVI82A=
I though that it will come down to implementing uninstall recipe. But
the question how will I trigger that recipe to run? Will I have to add
it to the node instead of the original?
On Mon, Aug 23, 2010 at 7:08 PM, Ryan Creasey
<
>
wrote:
>
Not in the way you would imagine a normal package manager to do an
>
uninstall. You would have to write an explicit cookbook::uninstall recipe
>
to handle the removal of a recipe. Basically have it undo everything that
>
your install recipe would do; there is no facility to "rewind" the actions
>
your Resources do automatically.
>
>
I thought it would be a cool idea to add this on the Provider level and it
>
seems possible on the abstract level, but when you sit down to implement
>
it... it gets complicated really fast.
>
>
- Ryan
>
>
On Aug 23, 2010, at 5:28 AM, Boris Shulman
>
<
>
>
wrote:
>
>
> Hello,
>
>
>
> I wonder if it is possible to trigger an undeploy action when removing
>
> role/recipe from a node?
>
> trigger
>
>
>
> Boris.
>
>
>
Archive powered by MHonArc 2.6.16.