v2.4.1

2.4.1 - 2018-02-09

Fixed

• cf_trace: true no longer messes up cf calls that are intended to capture the json output inside scripts. For now, we set CF_TRACE=false for all cf calls where we need to capture the output. I think there is a way to redirect the CF_TRACE output, but I couldn't figure it out with the way we do stdout and stderr redirects in the out script. Until then, please note that you won't see the trace info every cf command used in the script.