-
Notifications
You must be signed in to change notification settings - Fork 905
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
list - Sub-command should not require admin access (and not prompt) #1353
Comments
ferventcoder
added
0 - _Triaging
0 - Backlog
Improvement
and removed
0 - _Triaging
labels
Jul 5, 2017
@Skons I see what you mean - it could require elevation, if you are running anything but list. We should be able to handle this though. |
I was thinking there was a similar request for this enhancement (making listing not require admin) |
ferventcoder
changed the title
Choco list sources should not warn about elevated prompt
List sub-command should not require admin access (and not prompt)
Jul 5, 2017
This will be in 0.10.8 |
When researching this problem I came across issue #893 |
ferventcoder
added a commit
that referenced
this issue
Jul 9, 2017
When running the list subcommand, such as `choco source list`, it doesn't need admin privileges to provide read only information, so the check against whether a command may require admin privileges should be a bit smarter to see what sub-command it is about to run.
ferventcoder
changed the title
List sub-command should not require admin access (and not prompt)
list - sub-command should not require admin access (and not prompt)
Aug 29, 2017
ferventcoder
changed the title
list - sub-command should not require admin access (and not prompt)
list - Sub-command should not require admin access (and not prompt)
Aug 29, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When not providing -y the command does not continue but waits for input. When i provide -y i get a 20 second warning. When confirming with -y on the cli, i already confirmed the fact that i do not run an elevated prompt, and thus i should not get a 20 seconds timeout.
Also, it is not a function that really would require elevation.
The text was updated successfully, but these errors were encountered: