This would be the ideal but you *can* use the rpm provider when needed.
For example:
package { 'jdk':
ensure => installed,
provider => 'rpm',
source => '/pub/oracle/jdk-8-linux-x64.rpm',
}
This will install the rpm using the defined source path. In our
environment the /pub directory is available to all nodes via nfs.
On Thursday, March 2, 2017 at 8:03:11 PM UTC-5, LinuxDan wrote:
>
> +1
> To manage an RPM not in yum, put it into yum.
>
> > On Mar 2, 2017, at 11:02 AM, Garrett Honeycutt <
> [email protected] <javascript:>> 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
> >
> > --
> > 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] <javascript:>.
> > To view this discussion on the web visit
> 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.
>
--
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/a3b09ecf-da09-4c0c-9342-abe941d887e5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
