On Aug 22, 2:58 pm, Brad Krane <[email protected]> wrote:
> John,
>
> Thanks for the reply. I've tried all of your suggestions above,
> qualifying it as drupal6::drupal6::theme_repo and just theme_repo as
> well as putting the definition in its own file modules/drupal6/
> manifests/theme_repo.pp (and also using the three combinations of
> variable scoping) but I always get a similar result that it cannot
> find the resource.
>
> This behavior is very odd to me as I've used very similar definitions
> where they include other definitions of the same manifest with no
> issue at all but it seems that for whatever reason specifically with
> this module I get an error when I do so.
Then let's take a step back. Your class is rather complicated, and
all the details may be confusing (or even causing) the issue. For
example, you may have a nesting problem that is difficult to see in
all that code. I suggest putting each 'define' in its own file to
help make things clearer and more maintainable. Even before that,
however, I suggest getting a much simplified stub working, then
fleshing it out. So, does this work for you:
drupal6/manifests/init.pp
-----------------------------------
class drupal6 {
drupal6::theme_repo { "foo": }
}
drupal6/manifests/theme_repo.pp
------------------------------------------------
define theme-repo() {
}
?
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
