No, right now it has to be in the Secrets. In the next release it will be enabled by default and turning it off will be possible via env var (which is set before the
bitrise cli process, so it can’t be an env var specified in the config), Secrets (just like now) and bitrise CLI flag as well. But for now it can only be enabled via Secrets.
No, the filtering is done by the CLI itself, real time. The advantage is that this way the non filtered logs are not stored and not available for any tool, not for the website and not even in the build. The CLI (the open source “runner” which performs the builds / executes the build config inside a VM : https://www.bitrise.io/cli ) runs the commands in a way that all command outputs on StdOut & StdErr are go through the CLI’s filtering algorithm and only after that are printed / made available on any output.
No, it does not. If this secret is set when the build starts then the filtering mode will be enabled in that build. If you then remove it, the next build will run without filtering. Can be enabled/disabled any time.
Any time, we’re always happy to answer any questions you have