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
Describe what should be investigated or refactored
As described in the zarf documentation https://docs.zarf.dev/ref/actions/, mute is the correct field to set to suppress stdout. However, the documentation in the https://docs.zarf.dev/ref/actions/#action-transformations has an example where sensitive: true is set WITHOUT setting mute: true. This results in the stdout being displayed in the logs of something like a GitLab runner and potentially exposing secrets.
Describe what should be investigated or refactored
As described in the zarf documentation https://docs.zarf.dev/ref/actions/,
mute
is the correct field to set to suppressstdout
. However, the documentation in the https://docs.zarf.dev/ref/actions/#action-transformations has an example wheresensitive: true
is set WITHOUT settingmute: true
. This results in thestdout
being displayed in the logs of something like a GitLab runner and potentially exposing secrets.Additional context
The https://github.com/zarf-dev/zarf/blob/main/examples/component-actions/zarf.yaml#L128-L131 example does document how this should be done, but it might be as simple as updating the docs, or forcing
mute: true
whensensitive: true
is set.The text was updated successfully, but these errors were encountered: