github
Migrate to Vox Pupuli?
octocatalog-diff seems to receive almost no maintenance from GitHub. I opened a PR in July 2024 to make it work on current Ruby versions, and have received no response.
Would GitHub be open to move it to Vox Pupuli, an organization that maintains a whole lot of Puppet modules and Puppet-related tools? They have processes for adopting existing tools.
Mentioning @jhongturney because you did the most recent commits and releases.
voxpupuli already has their version of catalog diff at https://github.com/voxpupuli/puppet-catalog_diff. I think it may be better to move to using that, rather than maintain two different versions.
voxpupuli already has their version of catalog diff at https://github.com/voxpupuli/puppet-catalog_diff.
That tool is quite different though. It is meant to run on your Puppet Server, while octocatalog-diff is designed to be used in the code repository, either on your client or in CI.
I think it may be better to move to using that, rather than maintain two different versions.
@waipeng Vox Pupuli is primarily taking over existing Puppet modules and tools, not making their own. They have duplicate functionality in other areas.
That tool is quite different though. It is meant to run on your Puppet Server, while octocatalog-diff is designed to be used in the code repository, either on your client or in CI.
@mxey We are transiting over to catalog-diff; we run it the same way we are using octocatalog-diff. Two environments, one current and one with change, from a client. This is in CI.
The biggest change is in the presentation of the diff. We format the output from catalog-diff to try make it look like octacatalog-diff, but some team mates still prefer the old way 😄 .
can anyone, let me know what is preferred here ?
both tools looks like similar to me, the voxpupuli one needs to open the catalog api to access ? so any thing more to compare, like speed in compiling the catalog or the required env ?
