Thanks for the replies and being patient with me!
Maybe I'm thinking about this incorrectly, but it seems to me that
announcing a dependency ("I need x defined somewhere in order to work
properly") shouldn't require a class to declare the dependency as well. It
seems to me that the dependent class should not have to know anything about
how a particular dependency is defined, just that it is defined.
As an analogy to RPM package dependencies, if I have a package called
Django that requires a package which provides the "python" capability, the
Django package shouldn't need to include it's own version of Python. It
should be able to re-use any package which has the capability.
What does one have to do with the other?
>
You were suggesting using auto-lookups via Hiera to populate class
parameters, but we're using Foreman to populate those parameters. AFAIK,
there's no interoperability between Foreman's ENC and Hiera (without
writing my own).
Jon
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/e76b49ff-70f0-4b18-8b41-ecf853acef65%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
