can we get atom feeds of releases with ways to tag a release

Question

can we get atom feeds of releases with ways to tag a release as a migration

binford2k · Answer

gt ways to tag a release as a migration what would this mean

binford2k · Answer

like the difference between a major and minor semver release

Lumiere · Answer

so puppetlabs community moves a module to voxpupuli

binford2k · Answer

ooooo

bastelfreak · Answer

so so not only list in the old module this was migrated to also list in the new module this was migrated from

Lumiere · Answer

yes

bastelfreak · Answer

yes please

binford2k · Answer

sort of like how github does forks

binford2k · Answer

wrt to the backwards link

Lumiere · Answer

exactly I d love to differentiate between a forked migration and voluntary migration

bastelfreak · Answer

and if it was a migration at all

binford2k · Answer

that s something that keeps bubbling up and I think we re going to have to involve some of you in design conversations

binford2k · Answer

like what the most effective and also least surprising experience

Lumiere · Answer

for a voluntary migration I d just redirect same way that github does for a moved repo

Lumiere · Answer

for a forked migration I d say a warning lt Other User gt has marked that there may be a newer forked version of this module for community support

bastelfreak · Answer

a redirect is tricky when the new owner has a different understanding of semver and a new release in the new namespace breaks your setup

binford2k · Answer

I like that An authoritative that is the new version and an informational only I made this forked improvement

Lumiere · Answer

I agree but if it s a migration where both sides are in communication I feel like the risks are lower

bastelfreak · Answer

would also be nice if `puppet module list` would list modules as deprecated migrated

Lumiere · Answer

and the people who can add that mark should be like Vox PMC and PuppetLabs Community Managers with some process for the CM to mark a migration between non Vox entities

binford2k · Answer

that seems easy enough to do Right now we could add a deprecation marker

bastelfreak · Answer

also the right time to advocate for our rake tasks I guess <https github com voxpupuli ra10ke>

bastelfreak · Answer

maybe the whole `puppet module` thing should be deprecated

binford2k · Answer

admin permissions thread at <https puppetcommunity slack com archives CFD8Z9A4T p1685038313765169>

binford2k · Answer

I think that `puppet module` needs to exist because the ability to list modules is a core feature I m ok moving advanced features out kind of how some already moved to the PDK

Lumiere · Answer

there s a lot of documentation howto built around `puppet module install` too

bastelfreak · Answer

but in reality that s not used in most environments It s quite slow and most people use code manager or r10k or librarian puppet

bastelfreak · Answer

and the `puppet module build` face was already moved to a dedicated gem

bastelfreak · Answer

I understand that `puppet module list` is helpful and I also use that often to check if all the dependencies from the different metadata json files match up but maybe that s some logic that should be moved to r10k ra10ke and the face is just a wrapper around it

binford2k · Answer

or at least a gem

bastelfreak · Answer

yeah like the puppet modulebuilder

bastelfreak · Answer

ra10ke is already an awesome gem

Lumiere · Answer

if we re going that route should r10k be vendored into puppetserver directly and ra10ke or something like it be merged in to provide a puppet facet for managing r10k

bastelfreak · Answer

maybe vendored into puppet not puppetserver

Lumiere · Answer

sorry I mean the aio packaging

binford2k · Answer

not a bad idea Well outside of my decision making though grin

Lumiere · Answer

rather then the gem packaging

bastelfreak · Answer

yeah

Lumiere · Answer

it isn t like 90+ of users aren t using r10k

binford2k · Answer

this is quite the thread lolwut

binford2k · Answer

semi related have I ever shown you this POC <https prod puppet sneakernet k8s puppet net>

bastelfreak · Answer

brings up the question again why r10k is kinda deprecated not activly supported

bastelfreak · Answer

oh neat that s new to me

Lumiere · Answer

it seems like an obvious thing to just include as batteries r10k

Lumiere · Answer

and maybe once

binford2k · Answer

the sneakernet fork me link is broken btw <https github com puppetlabs puppet sneakernet>

bastelfreak · Answer

<https prod puppet sneakernet k8s puppet net> looks like our new beaker puppet helpers just as a web UI

binford2k · Answer

I m talking with edwin about potentially integrating it so that becomes a Forge API No promises on that though

binford2k · Answer

wrt to r10k I do believe we re getting more attention on it soon It s not clear what that attention will be though

bastelfreak · Answer

expect for arching the repo I m happy with every attention

bastelfreak · Answer

also given the PE support tickets I created I assume someone will work on r10k