- Feb 2021
Defaults names are given to steps without the :id options, but these might be awkward sometimes.
Why would those default names ever be awkward?
If you the default name is whatever comes after
then why can't you just change that name to whatever you want?
To answer my own question: I think you can do that, as long as the name is the 1st argument to
step. But below I noticed an example where a
Subprocesswas the 1st argument instead, and so it needs a name in this case:
step Subprocess(DeleteAssets), id: :delete_assets
Why are they inconsistent about calling it name or id? Which one is it? I guess it's an id since that's what the key is called, and since there's an
Id()helper to reference a task by its id.
The rsync and sleep commands (the sleep is just an example) are run through exec to prevent the creation of zombie processes if I kill the parent script while they're running, and each potentially-long-running command is wrapped in its own subshell so that when exec finishes, it won't terminate the whole script.