We often see this task fail in our CI runs, but since it has the no_log property, we don't have logging output that might be useful in helping to figure out why.
Is anyone else experiencing this? Also, it might be nice to have a var to control logging output for such tasks rather than assuming no_log: true.
We often see this task fail in our CI runs, but since it has the
no_log
property, we don't have logging output that might be useful in helping to figure out why.Is anyone else experiencing this? Also, it might be nice to have a var to control logging output for such tasks rather than assuming
no_log: true
.