Secret masking should be able to be toggled on and off for projects or an entire organization in the UI.
I would absolutely appreciate more granularity - it is currently masking out stack names (which are not secrets, especially for internal logs), so it appears to be very aggressive. Localized fine-tuning seems a bit of a must
Wholeheartedly agree, not every environment variable I use is actually a secret
See also: https://ideas.circleci.com/ideas/CCI-I-1223 .
(Having the ability to mark some secrets as not-really-secret, but just configuration)
This would actually make sense for specific steps, so it could be great to make it an option at the step/job level in the CircleCI configuration file.
You won't be notified about changes to this idea.