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
There is always a risk of leaking secrets to logs. It'd be cool if Samson could censor logs where secrets appear, to prevent accidental leakage, as well as flag those instances for further review.
The text was updated successfully, but these errors were encountered:
Ideally it would do that check before printing each line too ?
Then should also do it for the consolidated log once the deploy is finished.
It would check all used secrets values against the log.
I'm a little worried that this will get expensive, but maybe it's not too bad.
Another issue would be that the flow of the deploy needs to change, since we then cannot simply replace the secrets but have to keep track of them (env used + commands used)
There is always a risk of leaking secrets to logs. It'd be cool if Samson could censor logs where secrets appear, to prevent accidental leakage, as well as flag those instances for further review.
The text was updated successfully, but these errors were encountered: