Closed chelnak closed 2 years ago
Puppetfiles
.These results were generated with Rangefinder, a tool that helps predict the downstream impact of breaking changes to elements used in Puppet modules. You can run this on the command line to get a full report.
Exact matches are those that we can positively identify via namespace and the declaring modules' metadata. Non-namespaced items, such as Puppet 3.x functions, will always be reported as near matches only.
Merge of #548 needed followed by rebase before work on this can continue.
Puppetfiles
.These results were generated with Rangefinder, a tool that helps predict the downstream impact of breaking changes to elements used in Puppet modules. You can run this on the command line to get a full report.
Exact matches are those that we can positively identify via namespace and the declaring modules' metadata. Non-namespaced items, such as Puppet 3.x functions, will always be reported as near matches only.
@chelnak Thanks for working on that! How can I get this patch? Will this be added into future version? Here we still have version 5 from 2021: https://forge.puppet.com/modules/puppetlabs/vcsrepo
Hello hello!
I wanted to let it rest in main for a few days just to see if anything popped up.
I'll cut a release today 👍
@mfuhrmann v5.1.0 is up on the forge now 😄
After git was patched for CVE-2022-24765 the git binary would fail to execute in a repository that was owned by another user or group.
As of git 2.35.2, you can specify the
safe.directory
configuration or for prior versions define theGIT_CEILING_DIRECTORIES
environment variable to whitelist known directories.For users of VCSRepo running newer of git, there was no obvious way to apply the remediation.
This PR will close #535 by adding a
safe_directory
property to the type, allowing users to explicitly mark a path as 'safe'.