On Tue, Jan 24, 2012 at 4:42 AM, Walter Heck <walterh...@gmail.com> wrote:
> What if there was some standardised way modules expose a sort of list
> of requirements or an API of some sort?
I had this thought the other day, but more focused around the higher level
problem of dependency specification and consumption than Packages in
particular.
What if you made two functions:
1. declare_capability("foo")
This would essentially just create an empty resource, Capability[foo]. If
multiple modules tried to declare the same capability, it would error, just
like we do today with duplicate resources.
2. require_capability("foo")
This would just declare a requirement relationship to Capability[foo]. If
it couldn't find that resource, compilation would fail.
Wouldn't something like this solve the general problem? We don't really
want to just speak about packages, you generally want to be able to express
requirements like:
* This module requires a working SSH server
* This module requires a MySQL database
etc etc
I've deliberately focused this on doing this with functions as the
extension point as I think it keeps us focused, even if we decide that in
the future this should be solved in the metadata layer of a module.
--
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.
