Is there a way to capture a collection of shell commands that fail?

I have a collection of fab files that I use to manage servers, install applications on them, etc. for clients. Some of them are not very happy when I deliver the installation documentation as a file and readme. Usually there are experienced system administrators, not python programmers. If I could give them a bash script, which is a record of what the various fabfiles were doing, that would be great. Does anyone know a better way to do this?

I don't need help to manually translate fab commands to bash. I am looking for a programmatic way to capture a command stream, be it paramiko or fabric or on the most remote host.

+4
source share
1 answer

You wrote:

If I could give them a bash script, which is a record of what the various fabfiles were doing, that would be great.

and later

I don't need help to manually translate fab commands to bash. I am looking for a programmatic way to capture a command stream, be it paramiko or fabric or on the most remote host.

This will really help resolve your question in order to include a sample fab file and the desired result.

So, did you see this in the document? I could not find a place where this is mentioned, if the TEAM is a place holder or a literal, it would seem to be the owner of the place. (and I, perhaps, completely misinterpret the intention of the option, fab documentsers, more examples!)

-d COMMAND, --display=COMMAND Prints the entire docstring for the given task, if there is one. Does not currently print out the task's function signature, so descriptive docstrings are a good idea. (They're always a good idea, of course – just moreso here.) 

But it looks like you can get what you want by inserting the full command into docstring.

Hope this helps.

+1
source

All Articles