You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the new number format in front of every command i.e. '01' ,'02', ... it becomes very hard to tell where the command was executed when performing a Capistrano deployment with multiple roles.
It would be much clearer if the hostname was used as in place of the 'number' and makes debugging Puppet errors etc much quicker. Currently I have to tail the full capistrano.log at the same time in my deployments and it seems redundant.
It could be optional and enabled via a Capistrano option.
Hi, thanks for the feature suggestion! My goal with Airbrussh is to be as concise as possible, and while I definitely see the benefit in distinguishing the output of different servers, this does make things a bit more verbose, and potentially a lot of data gets lost by truncation when hostnames are long.
Hiding this behind a feature flag is not something I want to do, either. If we do decide to expand Airbrussh's formatting options, I'd rather make it pluggable than add flags.
I'll leave this issue open to gauge how much demand there is for this feature (readers: please 👍 if you are interested).
With the new number format in front of every command i.e. '01' ,'02', ... it becomes very hard to tell where the command was executed when performing a Capistrano deployment with multiple roles.
It would be much clearer if the hostname was used as in place of the 'number' and makes debugging Puppet errors etc much quicker. Currently I have to tail the full capistrano.log at the same time in my deployments and it seems redundant.
It could be optional and enabled via a Capistrano option.
i.e. basic WIP
Output:
The text was updated successfully, but these errors were encountered: