-
Notifications
You must be signed in to change notification settings - Fork 682
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
Windows default path format causes errors with inspec check #672
Comments
Huh. That is a bumper. We need to fix this. Thanks for reporting @grdnrio |
@chris-rock something I could take, perhaps? If so at what level would you change it? |
@mhedgpeth for sure. I try to write down the call history to help identifying the issue:
We need to find out, why the fetcher |
As I looked at it I thought that adding this line to
And in local, I would either just explicitly get rid of a "." at the start of the target or I would find a ruby-friendly way to understand that path. Is that the right approach? |
Yeah, that is the right approach. Looks like ruby does not resolve the relative paths properly. Once we know how to tackle it properly we should add that feature to the local fetcher. |
Oh yes. Ruby and expand_path and it's platform specific behavior is... hard. I'll try to poke at it this week. |
should be fixed by #963, please reopen if this continues to be an issue |
Description
Inspec check using autocomplete for paths in Powershell causes an error. Deleting the .\ dot and slashes works.
InSpec and Platform Version
Inspec version: 0.19.1
Windows 10 x64 1511
Replication Case
Possible Solutions
Workaround is to manually remove the backslahes and dot.
The text was updated successfully, but these errors were encountered: