-
Notifications
You must be signed in to change notification settings - Fork 2
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
Removed credentials from set_result event handlers #27
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we merge this fix... it affects demo (by leaking credentials..... )
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGMT. Please @taurus-forever check if the current output messages are fine with you.
@@ -42,7 +42,9 @@ jobs: | |||
|
|||
build: | |||
name: Build charms | |||
uses: canonical/data-platform-workflows/.github/workflows/build_charms_with_cache.yaml@v2 | |||
uses: canonical/data-platform-workflows/.github/workflows/build_charms_with_cache.yaml@v8.0.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We have already version 11 of shared workflows... but we need to have here renovate anyway... will be updated later. LGTM.
Issue
Credentials get printed to the terminal in plaintext when using s3-integrator. This causes a security issue during demos and video recordings.
(see DPE-3198 for more details)
Solution
Update event handlers/observers that print the credentials.
_on_sync_s3_credentials()
will instead display a message related to the action (e.g. "Credentials successfully updated")on_get_connection_info_action()
will replace the secrets with asterisks.