Secure env vars in build log
Hello,
I have a suggestion. If someone has an environment variable that is secure, it would be good if it showed up in the build log as ******* instead of the actual characters. That way if someone went to the trouble to encrypt and secure a value, it is never accidentally exposed through the build log.
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
Support Staff 1 Posted by Feodor Fitsner on 04 Jul, 2016 01:11 AM
Hi Tommy,
Thanks for the suggestion.
The could be an issue with implementation as secure variables behave absolutely similar to regular variables. The purpose of "secure variable" is to protect sensitive data in pull request builds of OSS projects that can be initiated by an untrusted party.
And current implementation is easy - variables marked as secure are just not set during PR builds.
Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 02:07 AM.