When a project's sendak.json says that it uses Fabric to finish, Sendak should have a Fabric wrapper that knows how to:
Read the location of the fabfile from the sendak.json.
Issue a fabric command that begins the finish process, e.g. fab deploy. (Whether this command name is a standard name, or whether it can be specified in its sendak.json, is not decided. Personal preference for the former until other requirements present themselves.)
Pass in any necessary arguments to that issues fabric command. This will include whatever Fabric needs to connect to the box and do work: a hostname, a username, potentially a port, and a path to the private key file on local disk.
I believe Fabric uses exit codes properly when a fab command succeeds or fails, but I haven't confirmed this.
When a project's
sendak.jsonsays that it uses Fabric to finish, Sendak should have a Fabric wrapper that knows how to:sendak.json.fab deploy. (Whether this command name is a standard name, or whether it can be specified in itssendak.json, is not decided. Personal preference for the former until other requirements present themselves.)I believe Fabric uses exit codes properly when a
fabcommand succeeds or fails, but I haven't confirmed this.