Re: [Puppet Users] Hiera values in provider
Thank you for the example. Right now I'm going a different route to avoid having to store the password locally in plaintext and switched to an approach where I parse and filter the output of "dnf repolist" which is "good enough" for our current usecase, but I will look into the nexus provider anyway to gain some more insights how they approach the whole provider implementation when interacting with a remote api. Best regards, Matthias On Tuesday, 2 August 2022 at 08:03:49 UTC+2 dhei...@opentext.com wrote: > Am Montag, dem 01.08.2022 um 12:47 -0700 schrieb Matthias K: > > > The provider subscribes and unsubscribes yum repo channels through a > > remote xmlrpc interface. To do this we need a username and password, > > this is part of the defined resource and comes from hiera. This is > > fine for creating the resources since we have all parameters > > available in the "create" method. > > Your provider can read arbitrary files on the agent it is running on. > This is what other providers also do, see the nexus3_rest module on > Puppet Forge for an example. It needs credentials to be able to manage > resources on a Nexus3 repository server, which it expects to be stored > somewhere in /etc/puppet. > > So essentially, in the class that uses your provider, create such a > credential/configuration file before using any resources your provider > provides. > > HTH... > > Dirk > -- > Dirk Heinrichs > Senior Systems Engineer, Delivery Pipeline > OpenText ™ Discovery | Recommind > Phone: +49 2226 15966 18 <+49%202226%201596618> > Email: dhei...@opentext.com > Website: www.recommind.de > Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach > Vertretungsberechtigte Geschäftsführer Gordon Davies, Madhu > Ranganathan, Christian Waida, Registergericht Amtsgericht Bonn, > Registernummer HRB 10646 > This e-mail may contain confidential and/or privileged information. If > you are not the intended recipient (or have received this e-mail in > error) please notify the sender immediately and destroy this e-mail. > Any unauthorized copying, disclosure or distribution of the material in > this e-mail is strictly forbidden > Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte > Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E- > Mail irrtümlich erhalten haben, informieren Sie bitte sofort den > Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie > die unbefugte Weitergabe dieser Mail sind nicht gestattet. > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/4a6bdfa0-d4e1-4b77-9ee6-7a232137fb69n%40googlegroups.com.
[Puppet Users] Puppet Platform 7.18.0 is now available!
The next release in the Puppet 7 series, Puppet 7.18.0, is now available! The release contains new features, minor enhancements, and bug fixes including: Agent 7.18.0 - Adds support for Ubuntu 22.04 (x86_64), macOS 12 (M1), and Windows 11 Enterprise (x86_64) - Puppet agent --disable is ignored with cron puppet agent (splay). Puppet agent now checks the disabled lock file after sleeping due to splay PuppetDB 7.11.0 - Query logging has been improved when log-queries is set to true. Now queries are logged with their UUID before they are parsed which makes debugging easier when there are PQL parsing issues - Fixed a bug that was introduced in 6.21.0 and 7.10.1 which caused upgrade failures with PostgreSQL hot standbys. The method of disabling the jit has been changed to avoid the problem Server 7.9.0 - Puppet Server now uses JRuby 9.3.4.0 For the full list of changes and detailed descriptions, check out the release notes: https://puppet.com/docs/puppet/7/release_notes_puppet.html#release_notes_puppet_x-7-18-0 -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CABRr%2Bm%2Bh-FJKe0KU8r1s_OsFuxKrWo8WPLh47KFDG51ZOdQ9JA%40mail.gmail.com.
[Puppet Users] Puppet Platform 6.28.0 is now available!
The release contains new features, minor enhancements, and bug fixes including: Agent 6.28.0 - Adds support for Ubuntu 22.04 (x86_64), macOS 12 (M1), and Windows 11 Enterprise (x86_64) - Puppet Agent now reloads its CA and CRL bundles every 30 minutes during each run. Previously it only loaded it when the process started, which meant the service had to be restarted if the CA/CRL files changed on disk PuppetDB 6.22.0 - Query logging has been improved when log-queries is set to true. Now queries are logged with their UUID before they are parsed which makes debugging easier when there are PQL parsing issues - Fixed a bug that was introduced in 6.21.0 and 7.10.1 which caused upgrade failures with PostgreSQL hot standbys. The method of disabling the jit has been changed to avoid the problem Server 6.20.0 - puppetserver http client respects include_system_store option. Puppet Server's Ruby HTTP client now supports loading certificates from the system trust store that is included with Puppet Agent. It also supports loading certs from a file or Java cert store at an arbitrary location via the ssl_trust_store setting - When the puppet user and group are created on rpm-based systems, they are now assigned a static UID/GID of 52. For the full list of changes and additional details, check out the release notes: https://puppet.com/docs/puppet/6/release_notes_puppet.html#release_notes_puppet_x-28-0 -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CABRr%2BmKah%3D5%2BaTh7WR%2Bra8am_OvvX15k3gyYQQj%3Dsru_HoZ-Bg%40mail.gmail.com.
Re: [Puppet Users] Puppet Platform 7.18.0 is now available!
Am Dienstag, dem 02.08.2022 um 17:04 -0700 schrieb Puppet Product Updates: > Adds support for Ubuntu 22.04 (x86_64), Thanks a lot for this. However, there's still no (Debian) Arm64 package available. Given the ever growing popularity of this platform, esp. on AWS, this is a pity. Bye... Dirk -- Dirk Heinrichs Senior Systems Engineer, Delivery Pipeline OpenText ™ Discovery | Recommind Phone: +49 2226 15966 18 Email: dhein...@opentext.com Website: www.recommind.de Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach Vertretungsberechtigte Geschäftsführer Gordon Davies, Madhu Ranganathan, Christian Waida, Registergericht Amtsgericht Bonn, Registernummer HRB 10646 This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E- Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind nicht gestattet. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/1b255d41dc24bf1d8fdf1774e044edff95e34a09.camel%40opentext.com.
