@David Sandilands we (vox pupuli) talked about it, but I think it's still unclear. I think it would be good to include them by default in facterdb but filter them out in rspec-puppet-facts when testing on Puppet 8

Zhenech: how familiar are you with foreman plugin and their packaging/asset generation?

I am not prepared for that question at this time of the day

Zhenech: awesome, will annoy you tomorrow

:>

9-15 CEST or GTFO ;)

:D

that is doable

👍

in the meantime, may I introduce you to my friend ehelms<tab> who isn't here but might help you in that other channel ;)

@bastelfreak and @David Sandilands I’ve not had time to finish it off, but https://github.com/puppetlabs/rspec-puppet/pull/53 is what you’re probably looking for.

This message was deleted.

@Alex Fisher what is actually missing?

so now that Puppet 7.25 is out and works with ruby-concurreny 1.x, I reverted our fix in gha-puppet and we can now add Puppet 8 support just by adding it do metadata.json

reverted PR: https://github.com/voxpupuli/gha-puppet/pull/31

https://github.com/voxpupuli/puppet-opensearch/pull/30 demo PR for adding Puppet 8

yo bastelfreak

what did you want w/ foreman plugin assets yesterday?

Zhenech: we (betadots, company I'm working for) have an open source web UI for viewing hiera data. Rails app with UI + API. We've a foreman smartproxy for it to query the API and a foreman plugin to extend forman to display hiera data for specific nodes

smart proxy plugin: https://github.com/betadots/smart_proxy_hdm . foreman plugin: https://github.com/betadots/foreman_hdm . hdm itself: https://github.com/betadots/hdm

uh-huh

both plugins itself are working now. It's a bit unclear how to package them properly. We've a ruby dev working on it and I think he doesn't know how the (react?) assets in the plugin are generated during packaging

I think he found some docs about it but all are from the pre-react time and now outdated

are you looking for debian or rpm packages?

both

are the plugins always released as gem and as deb/rpm?

sorta?

w/o a gem release, there is not really much to package ;)

but then you can have (deb|rpm)

yeah. I assumed we're supposed to release it as gem and then generate rpm/deb