-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Toggle off and on set -x when DOCKER_TOKEN is used #13293
Conversation
/publish connector=connectors/source-faker run-tests=false
|
/publish connector=connectors/source-faker run-tests=false auto-bump-version=true |
We do use DOCKER_PASSWORD in a few other scripts, but not via curl (e.g. |
Yeah, more importantly they are actual Github Secrets so GHA knows to mask them. The reason the tokens were an issue was because they are created during runtime.. |
probably should modify the following files as well: |
I dont see |
Fascinating! if we set an empty secret would github have masked the output even if we change the value in the script later? |
Codecov Report
@@ Coverage Diff @@
## master #13293 +/- ##
=========================================
Coverage ? 96.07%
=========================================
Files ? 2
Lines ? 51
Branches ? 0
=========================================
Hits ? 49
Misses ? 2
Partials ? 0 Continue to review full report at Codecov.
|
That might be the solution actually, yeah. |
Confirmed this removes logging of tokens |
* Toggle off and on set -x when DOCKER_TOKEN is used
What
This is why I'm not a fan of merging
set -x
into a repo :(Toggling it on and off whenever the
DOCKER_TOKEN
is used.How
Describe the solution
Recommended reading order
x.java
y.python