Closed DLeich closed 2 years ago
Huh. Now that I'm looking at the documentation for ra10ke again, it looks like you're using a :ref =>
for pinning to commits in the examples. It appears that passes the validate task, and actually works for r10k as well. I learned something new today. Leaving this issue open though in case anyone has thoughts about the usage of the commit parameter.
Is commit a valid syntax for r10k? Can probably add support to the validate task if it does. @DLeich
Easy to add support: https://github.com/voxpupuli/ra10ke/blob/master/lib/ra10ke/validate.rb#L50
Yes :commit
is valid: https://github.com/puppetlabs/r10k/blob/main/doc/puppetfile.mkd#git
It appears that the validate task will consider modules defined with a pinned commit to be in a failure state, even if the commit actually exists. We have a couple scenarios where this is necessary due to modules being either partially stale, or further development is being worked on. Yes, this is not the most ideal situation, especially if a module is getting stale from active development. However, I believe this to be a desirable feature nonetheless to support pinning to a specific commit. Take the following module definitions from a Puppetfile for example:
This results in the validate task in outputting:
If there's a configuration I'm missing to better support this, please let me know.