Hi,
I have a Puppet manifest which makes use of the tomcat::instance defined
type from the camptocamp/tomcat module on the Puppet Forge as follows:
class apps::reservations {
include tomcat
tomcat::instance { ‘reservations’:
ensure => present,
http_port => 8080,
}
}
However, when I run Puppet against a Vagrant VM, it tells me that the
tomcat class hasn’t been evaluated, so it can’t use tomcat::instance
(because of underlying failures when using the Tomcat module):
==> app: Warning: Scope(Tomcat::Instance[reservations]): Could not look up
qualified variable 'tomcat::instance_basedir'; class tomcat has not been
evaluated
This makes some sense to me, since I’m not defining an order in which
Puppet should run these resources. If the Tomcat module is not evaluated in
to the catalogue before I use the tomcat::instance resource, then failures
will occur.
How can I get Puppet to instantiate the Tomcat module first before then
looking to work with tomcat::instance? Adding the require metaparameter to
the tomcat::instance resource doesn't appear to do what I want it to do
(i.e. evaluate the include before using the resource).
I’ve seen a related problem before, and fixed that after a while, but this
one’s got me a bit stumped. It doesn't help either that I can't remember
how I fixed the last issue, even after looking through Git commits. Sad
times.
Thanks!
Andrew
--
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/bc3ce85e-cb13-4433-a328-bed561793d21%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
