-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
An issue #116
Comments
Leaving a comment |
Is your feature request related to a problem? Please describe. Log outputs include all inputText. If a flow includes a login, the resulting maestro.log will expose that password. Describe the solution you'd like Perhaps there should be an API: 'inputSensitiveText: password' If this is the case, the value of the field should be omitted or censored (XXXXXXXXX) in logging. For example if I have a sensitive text of value: Password1, I currently input it using this: maestro test login.yml --env=PASSWORD=Password1 test.yml
and logging outputs this as:
Perhaps we can update API and logging to look more like this: maestro test login.yml --env=PASSWORD=Password1 test.yml
and logging outputs this as:
Describe alternatives you've considered For my usecase, I am using GitHub actions and archiving the resulting failure logs from maestro. As a workaround, I can run some find and replace for any sensitive text before outputting the archive file. Additional context |
Issue
The text was updated successfully, but these errors were encountered: