Skip to content

Add --interactive flag to avoid future interactive prompts #5180

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.

Sign up for GitHub

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

Jump to bottom
Closed
tstromberg opened this issue Aug 22, 2019 · 0 comments
Closed

Add --interactive flag to avoid future interactive prompts #5180

tstromberg opened this issue Aug 22, 2019 · 0 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. ux/embedded Embedded UX blockers

Comments

@tstromberg
Copy link
Contributor

tstromberg commented Aug 22, 2019 •
edited
Loading

We don't have any interactive prompts right now, but we will soon for cases where the user needs to use sudo, but does not have rights to do so without interaction.

For example: Giving the hyperkit binary special permissions.

I suggest allowing users to select --interactive=false, to avoid the complication of weird flag combinations like --no-interactive=false.
@tstromberg tstromberg added ux/embedded Embedded UX blockers priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Aug 22, 2019
@tstromberg tstromberg changed the title Add flag to avoid interactive prompts Add --interactive=false support to avoid future interactive prompts Aug 22, 2019
@tstromberg tstromberg changed the title Add --interactive=false support to avoid future interactive prompts Add --interactive flag to avoid future interactive prompts Aug 22, 2019
@tstromberg tstromberg mentioned this issue Aug 22, 2019
Closed
@tstromberg tstromberg added priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. and removed priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Sep 4, 2019
@tstromberg tstromberg mentioned this issue Sep 16, 2019
Merged
@tstromberg tstromberg added the kind/feature Categorizes issue or PR as related to a new feature. label Sep 18, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. ux/embedded Embedded UX blockers
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@tstromberg