-
Notifications
You must be signed in to change notification settings - Fork 40
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
.puppet-lint.rc is ignored in module directories #804
Comments
I think I might be experiencing this same issue. I have a workspace open with multiple folders, one of which is puppet, and I'm finding that settings from When the puppet language server is started with the proper local-workspace when opened separately, everything works as expected...
When the puppet language server starts with what is the path to the first folder in the workspace when multiple paths are opened, it does not work (and starts the puppet language server with an invalid path, ignoring the
Any thoughts on how to make this work so I can get everything open in a single workspace? EDIT: If I edit the workspace file, and reorder the folders so the puppet repo is first in the list, the puppet server starts up with the expected workspace path. This allows me to work around it for now, but it still doesn't load other module directories / folders |
I'm having the same issue. Is there a fix so far? |
Just found the fix. If anyone is using vscode to open lots of repos in one workspace and if one the repos has puppet stuff inside, then puppet-lint doesn't honor your something like this: cd $HOME
ln -s my-workspace/puppet_repo_01/.puppet-lint.rc Then restart vscode and everything will work. Worked for me on MacOS, but I presume is no different on Linux or Windows (maybe). |
What Versions are you running?
OS Version: Windows 10
VSCode Version: 1.63.2
Puppet Extension Version:1.4.0
PDK Version: 2.3.0
What You Are Seeing?
I've my control repo cloned + all modules into that and the control repository is my workspace in vscode. Most modules have their own .puppet-lint.rc in their root directory with individual checks. VS Code with the Puppet extension seems to ignore them. I think it only reads the .puppet-lint.rc from the first directory in my workspace. But I currently have a hard time reproducing it.
What is Expected?
I would expect that the individual .puppet-lint.rc files are honored. This was mentioned in #111 but I don't understand the fix. Is it possible that I need to configure anything on my side or is this expected to work out of the box?
How Did You Get This To Happen? (Steps to Reproduce)
Output Log
It's an airgapped environment where I saw this. I will try to reproduce this in the next days and provide logs if possible.
The text was updated successfully, but these errors were encountered: