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 [email protected] 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: [email protected]
> 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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/4a6bdfa0-d4e1-4b77-9ee6-7a232137fb69n%40googlegroups.com.

Reply via email to