-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
exec resource: path param should default to the path fact #9440
Comments
Ah yeah, this is a common problem on Windows too, because you can't be sure where Windows installed. |
Hi @bastelfreak, thank you for reporting this issue. While we agree this is likely an improvement, we do not anticipate addressing this any time soon due to other issues demanding precedence. We may revisit this at a later time. If you are interested in submitting a patch to implement this issue, please open a pull request and link this issue. I've added the |
I implemented it in #9445 |
Signed-off-by: Tim Meusel <[email protected]>
Signed-off-by: Tim Meusel <[email protected]>
Signed-off-by: Tim Meusel <[email protected]>
Use Case
For some operations, exec resources are still common. The majority of exec resources I see use hardcoded paths like:
This often leads to problems because some distributions use
/bin
or/usr/bin
and others/usr/sbin/
. That makes it hard to write the resources for multiple operating systems. because of that I now mostly see this:I think
path => $facts['path'],
is repeated a lot. Because of that I think thepath
attribute should default to$facts['path']
when the user does not overwrite it.Describe the Solution You Would Like
Update
path
to default to$facts['path']
.Describe Alternatives You've Considered
Using absolute paths or always setting
path => $facts['path'],
.Additional Context
The text was updated successfully, but these errors were encountered: