On 07/19/2015 01:19 AM, Andrew Langhorn wrote:
>
> 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
>
Hmm, if the resource declaration is lexically preceded by an 'include
tomcat' then this should not happen.
In this case, the order in your manifest is really important. Is your
snippet truly representative of your actual code?
Regards,
Felix
--
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/55AAE9F5.5060503%40Alumni.TU-Berlin.de.
For more options, visit https://groups.google.com/d/optout.
