-
-
Notifications
You must be signed in to change notification settings - Fork 27
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
No support for sudo #8
Comments
It may be a nice idea to have the "Sudo" command. If it is detected in the recipe, it will be nice ask at first time, in beginning, and execute the sudo commands by that shell, when it is needed. I did not check how it is currently implemented - so I don't have any clue. Anyway ask the password, does not allow to automatize scripts and may be only useful in very narrow use cases. Another nice features - a bit of topic here:
Overall, the goals of the tool are nice. |
I think it should be possible for me to detect ahead of execution if the use of As for use via go-programs, I think that the godoc should be readable, but I suspect I'm not really suited to being used directly by other utilities. You can see cmd_run.go has the setup of a deployment - it's a little longer than it should be as it has to sort out:
If people do want to drive the packages via their code I'd support it to the extent that bug-reports come in. Your idea of allowing Apologies for the delay I've been traveling :) |
We connect as one user - often
root
- and have no facility for doing things as other users. Short of the obvious:It might be nice to allow "Sudo" as an alternative to "Run". Of course if we're prompted for a password it become complex again, quickly..
If we do go down this road we'd need:
At that point it might be worth taking a step back and removing
IfChanged
, instead addingIf
support. So we could just run:Of course that's a slippery slope, but perhaps one worth sliding down. Comments welcome.
The text was updated successfully, but these errors were encountered: