Prepare module for adoption by voxpupuli

[op-ct]

No description provided.

[ekohl]

Why was the module forked instead of transferred?

[op-ct]

Why was the module forked instead of transferred?

Because the Adopting a "puppetlabs" module process requires us to fork our own version and put it on the Forge first. Then they review the module, deprecate their version from the Forge, and point to ours

[bastelfreak]

this will probably bite us later on. maybe we should first merge pr hocon pr and then clean this up?

[op-ct]

@bastelfreak voxpupuli/puppet-hocon#1 should be ready for merge now 👍

[trevor-vaughan]

As far as I can tell, this looks like a reasonably straightforward port 👍

[binford2k]

@ekohl totally happy to talk about the process. Tbh, it was designed for adoption by unknowns, so if preferred, I think we can vastly simplify it for Vox. I'm happy to just transfer it if y'all want that instead.

[ekohl]

That sounds great. I think that means we have to delete this fork and then transfer it.

Also, given the dependency chain I'd prefer to start with puppetlabs-hocon and then update puppetlabs-puppet_authorization.

[bastelfreak]

@binford2k arent those two modules used by PE? Some months ago there was a discuasion in slack about hocon and puppet_authorization modules and the idea was to unarchive them because a commercial product drom Puppet uses them. I dont know if thats still the case.

[trevor-vaughan]

@binford2k Do you happen to have an update regarding the transfer? I agree with @bastelfreak that PE seems to use this but it needs to be updated regularly to stay viable as a public module.