I'm probably trying to solve a problem that I don't really need to
solve, but I'm hard-headed enough that I'm going ahead anyway...
I am using foo::params to centralize things like file paths, package
names, etc. that vary by $::osfamily, but I am running into
difficulties where the actual parameters might vary partly on
$::osfamily but within an OS family there might be other variations
not represented by facts.
Let's say I have a platform like Solaris where a particular software
package may be provided by several different parties and where I might
have perverse reasons for wanting to vary the package source-provider
on a system-by-system basis. Take Apache, for example: on one host
that's doing simple static file serving, I might use the 2.0 build
that is included with Solaris--minimizes dependencies, patches come
from OS vendor, etc.; on another Solaris box, a developer wants
something more complicated, so the 2.2 build from OpenCSW is needed.
And another developer wants Apache from Sunfreeware.
If stupid internal politics do not seem like an adequate
justification, let's say I'm building a module that I intend to
distribute via Puppet Forge, where I shouldn't just assume that
everyone will want his package from one vendor or the other.
How do you solve this?
Parameterized classes seem like the obvious answer, but what I've come
up with introduces an ordering dependency:
# init.pp
class testmod {
include testmod::params
info("\$testmod::params::whosit is '${testmod::params::whosit}'")
}
# params.pp
class testmod::params ($whosit = "foo") {
info("\$whosit got a '$whosit'")
}
This works:
class { 'testmod::params': whosit => 'barbarbar' }
class { 'testmod': } # or include testmod
But this results in "Duplicate declaration: Class[Testmod::Params] is
already declared":
class { 'testmod': }
class { 'testmod::params': whosit => 'barbarbar' }
as does node inheritance:
node basenode {
include testmod
}
node /./ inherits basenode {
class { 'testmod::params': whosit => 'burburbur' }
}
The best thing that I've come up with so far is to parameterize the
top-level class:
class testmod ($whosit = "foo") {
class { 'testmod::params': whosit => $whosit }
...
}
Which seems fine if the top-level class is the only thing to use the
testmod::params class, but that's unlikely in real life--I will
probably have a testmod::install class that uses the package name, a
testmod::service the uses the service name, etc.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
