There are a number of reasons it's not a great idea to put them in the module, but one is that if you start sticking binary artifacts into your Puppet code, the size of the repos(s) will grow a lot and it will be much slower to clone them. Also it's just not how people expect things to work.
Say you onboard a new member of your team and they need to deal with that RPM -- your Puppet module is probably the last place they would ever look for it. Beyond the technical reasons, I think this is an important one. The less snowflakey you can make your automation, the easier it's going to be for new folks to learn to work with it. Lots of good suggestions in the thread: setting up a Yum repo, or using an artifact repository like Artifactory or Nexus. At my last shop we used Spacewalk: http://spacewalk.redhat.com/ At my first job where I did Puppet like 4-5 years ago we had Solaris hosts that used a lot of custom packages. We served those up with just a vanilla HTTP server and used wget to pull them down in our Puppet code. Pretty ugly but still better than checking them in with the modules themselves. Whenever you can leverage your OS's native packaging system, you're going to make it easier on yourself and your coworkers. Rich On Thu, Mar 2, 2017 at 6:58 AM, warron.french <warron.fre...@gmail.com> 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 > > -- > 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/CAJdJdQkTwF4HTh8r54HZ_aNittaLZ7UMEKEZTEgpaJ9vU8R5mw% > 40mail.gmail.com > <https://groups.google.com/d/msgid/puppet-users/CAJdJdQkTwF4HTh8r54HZ_aNittaLZ7UMEKEZTEgpaJ9vU8R5mw%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 puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAGceorzKTWGFQBHRoAn27wj9WU6VFcr%3DySqkZBUwASV%3DKGjRNQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
