-
Notifications
You must be signed in to change notification settings - Fork 19
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
Add CLI option to override shell used #118
Conversation
As noted in saschagrunert#117, we want to override the shell that's used. In the case that we want to override the shell, we unfortunately run into the fact that `Ensure` requires `bash`. We can start by defaulting to using `sh`, which should be fairly safe as a drop-in.
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #118 +/- ##
==========================================
+ Coverage 71.86% 72.80% +0.94%
==========================================
Files 3 3
Lines 231 239 +8
==========================================
+ Hits 166 174 +8
Misses 41 41
Partials 24 24 |
Thank you! The lint CI is not happy unfortunately. |
d1092e2
to
3d0d038
Compare
3d0d038
to
beb0dde
Compare
beb0dde
to
0204af2
Compare
The linter now complains about the line length 🙃 |
Sorry yeah just trying to sort - unfortunately my local Go version isn't compatible with I'm trying to use a Docker container in the meantime! |
As noted in saschagrunert#117, we want to override the shell that's used. To do so, we can continue using the default of `bash`, but allow overriding it with the `--shell` flag. We need to disable the gosec finding for the new shell argument: G204: Subprocess launched with a potential tainted input or cmd arguments (gosec) As we're comfortable with the risk, as it runs on the user's machine. Closes saschagrunert#117.
0204af2
to
0de93d7
Compare
Thank you 🚀 |
sh
forEnsure
Closes #117.