Skip to content
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

Factor in --interactive flag value in driver autodetection #7215

Closed
tstromberg opened this issue Mar 24, 2020 · 1 comment
Closed

Factor in --interactive flag value in driver autodetection #7215

tstromberg opened this issue Mar 24, 2020 · 1 comment
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

Some drivers may require an interactive installation. The driver detection should take this into account.
@tstromberg tstromberg added 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 labels Mar 24, 2020
@priyawadhwa priyawadhwa added the kind/feature Categorizes issue or PR as related to a new feature. label Mar 25, 2020
@tstromberg
Copy link
Contributor Author

This will implicitly happen with #7216 - drivers that require interaction will fail and move on to the next driver.

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
2 participants
@tstromberg @priyawadhwa