-
Notifications
You must be signed in to change notification settings - Fork 150
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
feat(cli): Add meltano config --unsafe
flag
#7984
feat(cli): Add meltano config --unsafe
flag
#7984
Conversation
…tings in command output
✅ Deploy Preview for meltano ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Didn't know whether to keep the yellow styling for sensitive values when they are exposed (as a kind of reminder that the value is still sensitive) or not, so I just made it output what it otherwise would have before #7878. Pretty easy to change if anyone feels strongly. |
Codecov Report
@@ Coverage Diff @@
## main #7984 +/- ##
=======================================
Coverage 89.47% 89.48%
=======================================
Files 295 295
Lines 21791 21810 +19
Branches 2440 2441 +1
=======================================
+ Hits 19498 19517 +19
Misses 1937 1937
Partials 356 356
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
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.
LGTM!
meltano config --unsafe
flagmeltano config --unsafe
flag
Essentially bypasses behaviour changes made in #7878 to expose sensitive setting values with
--unsafe
, as per this request on Slack by @visch.