Mask environment variable secrets in command-line logs#283
Conversation
This change introduces a `Mask` function in the `cmd` package that identifies leading environment variable assignments in a command line string and replaces their values with `[MASKED]`. The `runExec` helper in the `build` module is updated to use this function when logging commands, ensuring that sensitive information like API keys or passwords passed via environment variables are not leaked into the build logs. Comprehensive unit tests for `cmd.Mask` and a regression test for `runExec` are included.
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
1 participant
Implement secret masking for command-line logs to prevent sensitive information (e.g., API keys, passwords) passed as environment variables from being exposed in build logs. This includes a new
cmd.Maskfunction and its integration into the project's build helpers.PR created automatically by Jules for task 3333875199693607752 started by @pellared