Puppet users - Nov 2013 - managing puppet module dependencies

with maven, you can tell that a project requires a list of artifacts and 
their versions.
those dependencies in turn have other dependencies.
maven takes care of managing all this.
for instance, maven can find out if two of your dependencies requires a 
conflicting version of another dependency.


is there a similar thing in puppet?


i''ve read about https://github.com/rodjek/librarian-puppet
but it seems that you need to define yourself the direct dependencies and 
recursive dependencies.
and you cannot query about conflicting version dependencies.
is that correct?



-- 
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 puppet-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/95597d95-0b8a-4173-8f02-20fcc84850f5%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

On Mon, Nov 18, 2013 at 8:39 AM, David Portabella <
david.portabella@gmail.com> wrote:
> with maven, you can tell that a project requires a list of artifacts and
> their versions.
> those dependencies in turn have other dependencies.
> maven takes care of managing all this.
> for instance, maven can find out if two of your dependencies requires a
> conflicting version of another dependency.
>
Hi David,

With the Puppet Forge, module authors are expected to express dependencies
on other modules via their module metadata. The logistics for this are
documented here:
http://docs.puppetlabs.com/puppet/latest/reference/modules_publishing.html#dependencies-in-the-modulefile

>
>
> is there a similar thing in puppet?
>
>
> i''ve read about https://github.com/rodjek/librarian-puppet
> but it seems that you need to define yourself the direct dependencies and
> recursive dependencies.
> and you cannot query about conflicting version dependencies.
> is that correct?
>
Tools like the built-in Puppet Module Tool and librarian-puppet use that
dependency metadata during installation to ensure that you have everything
you need to use the module. The module tool will do its best to prevent
conflicts during install and will show you what conflicts currently exist
in your modulepath when you run `puppet module list`. It does not provide
the ability to determine version conflicts before installing.

-- 
Ryan Coleman | Modules & Forge | ryanycoleman on twitter & #puppet IRC

-- 
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 puppet-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/CAFkZv1uuvj5JnW6cZERtjFGJvoSqC-kJVcmbuPj%3DqccechJHZQ%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.