Skip to content
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

Kitchen escaping spaces in path names and then using them as literal (Windows) #2899

Open
minsis opened this issue Jul 20, 2022 · 0 comments
Labels
Status: Untriaged An issue that has yet to be triaged.

Comments

@minsis
Copy link

minsis commented Jul 20, 2022

Description

Running kitchen using windows version of workstation

Running kitchen from a path that has a space in it, kitchen will then escape the path, then try to use the escaped path as a literal path in other commands which then fails the process.

image

In the screenshot you can see that it has identified the policy file, then has escaped the spaces in it, then tried to use that escaped path as a literal by quoting around it. If I run chef-cli.BAT install without the escaped path it generates the lock file just fine.

Chef Workstation Version

Chef Workstation version: 22.7.1006
Cookstyle version: 7.32.1
Chef Infra Client version: 17.10.0
Chef InSpec version: 4.56.20
Chef CLI version: 5.6.1
Chef Habitat version: 1.6.420
Test Kitchen version: 3.3.1

Platform Version

Windows 10

@minsis minsis added the Status: Untriaged An issue that has yet to be triaged. label Jul 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Untriaged An issue that has yet to be triaged.
Projects
None yet
Development

No branches or pull requests

1 participant