Repositories should _never_ contain binary objects. The only exception I
ever allow my developers is graphical assets related to websites.

On 03/02/2017 08:48 AM, warron.french wrote:
> Garrett, thanks.
> 
> So, to clarify for myself in terms of a BEST practice are you declaring
> "don't deliver RPMs as part of the payload of the Puppet Module?"  *I
> just got that part working.  :-/*  I don't mind correction, but I don't
> want to go down the rabbit hole.
> 
> Secondly, using an exec resource to implement the RPMs?
> 
> Perhaps something like this...
> 
> exec { 'install_cctk_rpms':
>          creates => '/opt/dell/dcc/cctk',
>          command => 'yum localinstall -y A.rpm B.rpm',
>          returns => '0',
> }
> 
> I have never written an exec resource declaration before.  Can you tell
> me if the exec syntax is correct, and that it is also what you meant for
> having to commands; I can combine them into a single *yum localinstall
> -y  *command correct?
> 
> Thanks Garrett.
> 
> 
> --------------------------
> Warron French
> 
> 
> On Thu, Mar 2, 2017 at 11:02 AM, Garrett Honeycutt
> <[email protected] <mailto:[email protected]>> wrote:
> 
>     On 3/2/17 9:58 AM, warron.french wrote:
>     > Hello all,
>     > can someone please advise me on a proper set of syntax (a file to look
>     > at) for an example to follow to solve the following challenge:
>     >
>     >  1. I have 2 deliver 2 *.rpm files that are not in a YUM
>     repository, so
>     >     I dropped them into the files directory of my module path.
>     >  2. I need to be able to execute each of them either together, or
>     >     _A.rpm before B.rpm_
>     >  3. __Then execute a shell script that requires the 2 RPMs to be in
>     >     place before that happens.
>     >
>     > I am starting to get into slightly more complicated modules, instead of
>     > simply delivering basic ASCII text files using  *content =>
>     > template('modulename/some.erb')*.
>     >
>     > I just need an example that is know to provide proper execution, proper
>     > syntax, and something I can learn from correctly.  I am still building
>     > the foundation of my understanding, so troubleshooting someone else's
>     > code isn't going to be too good for my development yet.
>     >
>     >
>     > Thank you in advance,
>     > --------------------------
>     > Warron French
>     >
> 
>     Hi Warron,
> 
>     What you want to accomplish is a bad idea and you should use a yum repo
>     and definitely not check in binary data with your modules. You could at
>     least store the rpm's somewhere and then download them from that
>     canonical source. Take a look at Artifactory which can help with where
>     to store things such as your random rpm's.
> 
>     Sometimes you have to automate what you have before you build something
>     better. Suggest writing an exec resource that can handle what you are
>     trying to do. The key here is to have two commands. One that checks to
>     see if you are already in the desired state and another to get you to
>     the desired state. Figure that out without Puppet and once you have
>     those commands, you can write a manifest.
> 
>     Best regards,
>     -g
> 
>     --
>     Garrett Honeycutt
>     @learnpuppet
>     Puppet Training with LearnPuppet.com
>     Mobile: +1.206.414.8658 <tel:%2B1.206.414.8658>
> 
>     --
>     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]
>     <mailto:puppet-users%[email protected]>.
>     To view this discussion on the web visit
>     
> https://groups.google.com/d/msgid/puppet-users/4fc045bb-3e5f-f9d4-88a6-688ca3e3436b%40garretthoneycutt.com
>     
> <https://groups.google.com/d/msgid/puppet-users/4fc045bb-3e5f-f9d4-88a6-688ca3e3436b%40garretthoneycutt.com>.
>     For more options, visit https://groups.google.com/d/optout
>     <https://groups.google.com/d/optout>.
> 
> 
> -- 
> 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]
> <mailto:[email protected]>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/CAJdJdQkCQJ%2BXE2th_OLyu7%2BZyJDROfyht9UC906_JXRn%3D0Q7Dg%40mail.gmail.com
> <https://groups.google.com/d/msgid/puppet-users/CAJdJdQkCQJ%2BXE2th_OLyu7%2BZyJDROfyht9UC906_JXRn%3D0Q7Dg%40mail.gmail.com?utm_medium=email&utm_source=footer>.
> For more options, visit https://groups.google.com/d/optout.

-- 
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/4c9c1b1a-377a-8579-c7d3-a36e4488eebd%40bardicgrove.org.
For more options, visit https://groups.google.com/d/optout.

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to