-
Notifications
You must be signed in to change notification settings - Fork 3
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
Errors running puppet-check when metadata.json misses requirements #3
Comments
After some more investigation and code reading: at least the error For the other error |
First issue: I checked the source code and, strangely enough, my comment dictates the correct behavior but the code doesn't seem to follow it. It is a quick fix. Second issue: It looks like rubocop is using a yaml gem that comes with puppet instead of the one that comes with ruby. This could be an issue with rvm/rbenv gem loading. |
First issue: This actually revealed that i have redundant code in the related method, and I don't know how I missed that when it is the first Reek warning for the file. Second issue: Looking at it again, there is a possibility that you have an invalid |
First issue fixed in 26f3831. I recommend directly patching data_parser.rb as part of the Dockerfile for the image your are building as it will be a while before 1.4.0 since that will be the 'octocatalog-diff' release. |
Thanks a lot for looking into it and I'm very sorry to have mixed two unrelated issues in one ticket.
There is no |
Yeah, it did seem like an environment issue. The stack trace makes it seem like Rubocop is trying to load in a config file, so if there was some way to block that it might fix the issue. |
In one of our Puppet modules
puppet-check
fails with the following errors:or
We're using the Docker image found under https://hub.docker.com/r/vshn/puppetci/. It brings
puppet-check
pre-installed. The source Dockerfile which builds this image is here: https://github.com/vshn/docker-puppetci/blob/master/Dockerfile3Thanks for your help.
The text was updated successfully, but these errors were encountered: