Migrate to Vox Pupuli?

[mxey]

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.

[waipeng]

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.

[mxey]

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.

[waipeng]

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 😄 .

[ashish1099]

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 ?

[bastelfreak]

@waipeng Vox Pupuli is primarily taking over existing Puppet modules and tools, not making their own.

We maintain enough tools that we started on our own :)

That tool is quite different though. It is meant to run on your Puppet Server

https://github.com/voxpupuli/puppet-catalog_diff compares catalogs. They can be provided as JSON on the CLI, come from PuppetDB or from two different puppetserver API endpoints. But the tool doesn't have to run on a puppetserver.

My opinion as a Vox Pupuli member might be biased, but I recommend puppet-catalog_diff, because it's maintained. I originally discovered this ticket because it's used by onceover-octocatalog-diff. But the dependencies here are really out of date and it's not useable anymore in modern environments.

[mxey]

We maintain enough tools that we started on our own :)

True. What I meant is that Vox Pupuli often functions as the adopter of otherwise unmaintained Puppet things :)

They can be provided as JSON on the CLI, come from PuppetDB or from two different puppetserver API endpoints. But the tool doesn't have to run on a puppetserver.

@bastelfreak But it does need the Puppet code to be deployed to a Puppetserver, right? What I like about octocatalog-diff is that it can compile on the client, without having to push your code first, allowing shorter faster feedback cycles. Would it be feasible to add that to catalog_diff?

[bastelfreak]

If you want that the puppetserver compiles a new catalog for you, it also needs your code. It's not too much work to add an option to compile the catalog locally, but then you also need to pass the factset(s) for the node(s).

[ashish1099]

@bastelfreak should I create a ticket on voxpupuli repo for this issue, I would honestly like to compile on the client side

[bastelfreak]

Yes please (or even provide a patch :))