I see the scare quotes ;) but just in case, I do want to make sure
people know this was added in 0.9.2, it's actually the very first item
in the changelog! :)
http://docs.fabfile.org/0.9.2/changes/0.9.2.html
Anyway, as mentioned, it may not be ideal for all purposes, and I
expect in future editions we'll probably be breaking it out some so
people can mix it into their own code more easily.
For now, the key to making your own code work is simply to .close()
and then delete the key/value from fabric.state.connections, in order
that the next connection works correctly.
-Jeff
On Tue, Oct 19, 2010 at 11:09 AM, Jeff Honey <[email protected]> wrote:
> Wow...nice "undocumented" feature! ;-)
>
> I will still need to validate the system is available before moving to the
> next host, though.
>
>
> --
> ¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤
> ¤ kyoboku kazeoshi ¤
> ¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤
> ________________________________________
> From: [email protected] [[email protected]] On Behalf Of Jeff Forcier
> [[email protected]]
> Sent: Tuesday, October 19, 2010 11:01
> To: Jeff Honey
> Cc: [email protected]
> Subject: Re: [Fab-user] simple test loop.
>
> There's actually a built-in reboot function in Fabric which does the
> right things regarding the connection objects,
> fabric.operations.reboot (it's part of fabric.api, as usual). You
> might want to look into using that.
>
> If you need to tweak how it works or just use it for a reference,
> here's the code:
>
> http://github.com/bitprophet/fabric/blob/0.9/fabric/operations.py#L620
> _______________________________________________
> Fab-user mailing list
> [email protected]
> http://lists.nongnu.org/mailman/listinfo/fab-user
>
--
Jeff Forcier
Unix sysadmin; Python/Ruby developer
http://bitprophet.org
_______________________________________________
Fab-user mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/fab-user
