-
Notifications
You must be signed in to change notification settings - Fork 293
Add --non-interactive flag and improve TTY detection #1553
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
Open
tashian
wants to merge
8
commits into
master
Choose a base branch
from
carl/tty-detection-674
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+98
−32
Open
Changes from 1 commit
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
2418bad
Add --non-interactive flag and improve TTY detection
tashian 095867f
Merge branch 'master' into carl/tty-detection-674
tashian b119584
Don't hardcode password flag in non-interactive error
tashian ed500cc
Propagate --non-interactive flag to environment variable
tashian 5795a14
Remove error param
tashian 8676497
More specific hints when using non-interactive mode
tashian f98fc9d
Merge branch 'master' into carl/tty-detection-674
tashian c5454ee
Remove unused errs import and local replace directive
tashian File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.
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 could be confusing if the flag / file is different for a specific command. I believe
passwordandpassword-filewill work for most cases, and it's certainly better than what we do today, but there can be edge cases requiring different fields. It's possible this approach works for all uses ofpemutil.PromptPasswordandjose.PromptPassword, but it'd be best if the changes incli-utilscan also accomodate other use cases.It would be better if the actual flag/file were passed based on (the context of) the command that is being executed. Also see #688, which was stuck on passing that.
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.
I think I was able to address what you're asking for here, @hslatman, but take a look. It's definitely a bigger PR but the error messages are more contextually helpful now.