This message was deleted.

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

Yes, if you look at my comment (same username) , 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 @bastelfreak, 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.

Let's not start bickering.

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.

Thank you, that helps.

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 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 :-)