Brad.
Using the virtual::createsysuser worked.
Thanks again,
Paul
On Wed, Sep 7, 2011 at 1:11 PM, Brad Krane wrote:
> Paul,
>
> I'm not exactly sure, but from your class setup it looks like the
> createsysuser resource would have the full scope of
> accounts::virtual::createsysuser and should
Paul,
I'm not exactly sure, but from your class setup it looks like the
createsysuser resource would have the full scope of
accounts::virtual::createsysuser and should be referenced by
virtual::createsysuser and not just createsysuser when it is used in
accounts::appaccts.
Cheers,
On Sep 2, 7:28
On Sep 2, 1:21 pm, Brad Krane wrote:
> Here is a very simple manifest that recreates this error:
>
> class foo {
> define bar ( $val ) {
> notice("bar($val)")
> }
>
> }
>
> $some_hash = { 'name' => "some_name" }
>
> foo::bar { "$some_hash['name']": }
>
> Puppet::Parser::AST::Resource fai
I'm also seeing the same problem I believe.
I'm running on the following
puppet 2.7.3
ruby 1.8.5
centos 5
I have a defined resource in the module called accounts
class accounts::virtual {
define createsysuser ($val) {
...
}
}
In another class in the same module, I have
Here is a very simple manifest that recreates this error:
class foo {
define bar ( $val ) {
notice("bar($val)")
}
}
$some_hash = { 'name' => "some_name" }
foo::bar { "$some_hash['name']": }
Puppet::Parser::AST::Resource failed with error ArgumentError: Invalid
resource type foo::bar a
I have spoken too soon about the nil value causing the problem. When I
set the default value from nil to "something" the error came back. It
seems that just using a hash value in the name to be expanded is what
the real issue is.
--
You received this message because you are subscribed to the Goog
> 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 c
On Aug 22, 2:58 pm, Brad Krane 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
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 alway
On Aug 19, 1:33 pm, Brad Krane wrote:
[...]
> drupal6/manifests/init.pp
>
[...]
> class drupal6 {
[...]
> define theme_repo(
> $theme = "",
> $version = "",
> $site = "default",
> $upstream = "drupal")
> {
[...]
10 matches
Mail list logo
