-
Notifications
You must be signed in to change notification settings - Fork 2.2k
feat(hubble): ignore uuid and secret while push again #2790
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
Conversation
Codecov Report
@@ Coverage Diff @@
## master #2790 +/- ##
==========================================
+ Coverage 87.89% 88.00% +0.11%
==========================================
Files 138 138
Lines 9402 9457 +55
==========================================
+ Hits 8264 8323 +59
+ Misses 1138 1134 -4
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
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.
- this does not considered multiple uuid will have different secret
- secrets are stored in plain text, not secure.
- missing test
- this PR should be targeted at
refactor-hub-cli
@hanxiao I don't understand this problem? Now, each folder only contains one executor, and so only one uuid should be considered. |
5a1b671
to
2e2ec0e
Compare
820b9c3
to
e4f8624
Compare
Now, everytime the user want to update the executor, the
--force
and--secret
options is required:I don't think it is a good UX experience. I think, the
UUID8
andSECRET
info can be tracked in a local file, so that the user can directly update executor in hubble without typingUUID
repeatly.┆Issue is synchronized with this Asana task by Unito