Puppet Community

Any chances of getting  Amazon Linux 2023 in PE ? Folks want to use it and 'not supported by puppet' is not a good look :disappointed:

It's something we're tracking but I don't have a ticket to refer you too yet.

:allthethings: Next up is _:teacher: Bolt_ in <https://www.timeanddate.com/worldclock/converter.html?iso=20230425T220000&amp;p1=202&amp;p2=179&amp;p3=919&amp;p4=307&amp;p5=3332&amp;p6=236&amp;p7=240|4 hours>

I'll post back here when I have public Amazon Linux 2023 tickets to refer to

Alright folks, that's a wrap! See you back here in 2 weeks

I’ll miss the Bolt office-hours so I’ll write the question in advance.. here in the issue <https://github.com/puppetlabs/bolt/issues/3200> a person is trying to implement the `delete_file()` Bolt function. I’m trying to help the person as much as I can but I’m not that good in the Bolt internals. May I have someone from the Bolt team there for support please?

:letsplay: _:teacher: Bolt_ is about to start up in 15 minutes

:beaker: Next up is _:teacher:Puppet Forge_ in <https://www.timeanddate.com/worldclock/converter.html?iso=20230427T180000&amp;p1=202&amp;p2=179&amp;p3=919&amp;p4=307&amp;p5=3332&amp;p6=236&amp;p7=240|43 hours>

:letsplay: _:teacher:Puppet Forge_ is about to start up in 15 minutes

I read <https://thehackernews.com/2023/04/hackers-flood-npm-with-bogus-packages.html|this article> the other day and it made me happy that we're working on some security and anti-bot defenses for the Forge.

ah speaking of that. I've something for you

I had a longer talk with the <http://rubygems.org|rubygems.org> people and their lacking org support and how we should handle secrets as vox pupuli

because we adopted a puppet lint plugin that enforces 2FA

<https://github.com/rubygems/rubygems.org/pull/3716> they are working on OIDC support which enables us to use github to authenticate to rubygems and use the tokens from a github CI run to request a short lived rubygems api key

and probably much more that I mixed up and forget

is there anything related planned for the forge

interesting. That would mean that github could publish modules without a persistent API token?

so you would allow that github user A or a group gets rubygems access. then the CI pipeline is able to get a short-lived token

I like that idea a lot and will add investigating it to our backlog. Heads up though, we've got a fair amount of work on tech debt before we'll be able to add net new features

they have a nice slack where their devs respond

(this office hour is for the Forge, not for modules. but I can help there too.)

I see that change in 13.0.0, not 13.1 <https://github.com/puppetlabs/puppetlabs-mysql/blob/main/CHANGELOG.md#v1300-2022-08-25>

The PR that added that has some explanation. <https://github.com/puppetlabs/puppetlabs-mysql/pull/1449>

I've not tried to override it myself. Are you saying that using the `package_name` doesn't work as documented?

and to install commercial, I would assume that enabling the proper repositories (probably with apt::source, since it sounds like you're on ubuntu) and then using the proper `mysql-commercial-server` package name would work.

Yes, if you look at my comment (same username) , <https://github.com/puppetlabs/puppetlabs-mysql/pull/1449|in the link you provided here> you'll see that myself and one other person were unsuccessful using that AND that it caused major issues in production.

that indeed was released in 13.0.0, not 13.1.0

ok. Well then you know why it was introduced then, lol.

Thank you <@U1PC2RAH0>, as usual your comments are extremely helpful and relevant to the problems at hand.  Please kindly stop replying to any posts from me. Thank you.

in any case, Lukas (one of the developers on the content team) asked if you'd file a ticket  raising any current problems. Is there a ticket about it?

No, but I will.  I'll need to upgrade out of 12.3 sooner or later, as I'm sure other's will too.

You mentioned using apt::source,, I've never used that.  Is there any documentation on  how I would implement that?

There's an example in the README showing how to enable the official mariahdb repos. You should be able to use something similar to get commercial. <https://github.com/puppetlabs/puppetlabs-mysql#install-mariadb-on-ubuntu>

Thanks for the example. But now I have so many more questions.  I can see the class declaration and I know where that goes in the manifest. But where does the apt::source code go?  Another manifest in the mysql module? Into the same manifest as the class declaration below it?  Somewhere else?  The problem with documentation like this is that it assumes so much.  This sentiment was echoed by everyone in the puppetlabs sponsored courses I attended last year.

Also, it's all mariadb again.  Has puppet considered making a separate mariadb module?

that is an example of using apt::source to enable a repo that happens to be mariahdb.

You can manage any repo with similar code.

fwiw, we are designing UX that will help surface the foundational docs alongside modules on the Forge to help clarify the module specific docs

Thank you, that would certainly help to clarify things for people starting out.  Or, like me with 1 year experience and several courses and behind their belt who still get confused by the documentation. It really makes the learning curve that much steeper.

It’s best to assume people know nothing when writing documentation.  Heck, even a “where could this code go?” Feature would help.  

it is something were looking into since we recognise people are coming to the forge to build something not just to get the one piece and the docs tend to be more technical reference based rather than implementation based. So watch this space and please raise tickets for docs if they could be better :-)

oh interesting. Reading through <https://docs.github.com/en/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect|the docs> implies that there's a high probability that we could reuse some Relay work to support this.