search

example42 / puppet-firewall

Example42 Firewall abstraction meta-module
http://www.example42.com
Other
3 stars 11 forks source link

Dependencies are not published on Puppet Forge #1

Closed codeaholics closed 11 years ago

codeaholics commented 11 years ago

This module depends on your iptables module, but the iptables module is not published on Puppet Forge, hence:

$ puppet module install example42-firewall --modulepath=./modules
Preparing to install into /home/danny/workspace/puppet/modules ...
Downloading from http://forge.puppetlabs.com ...
Error: Could not install module 'example42-firewall' (latest: v2.0.0)
  No version of 'example42-iptables' will satisfy dependencies
    'example42-firewall' (v2.0.0) requires 'example42-iptables' (>= 2.0.0)
    Use `puppet module install --ignore-dependencies` to install only this module
$
codeaholics commented 11 years ago

More generally, this appears to apply to several modules. For example, the ActiveMQ module depends on the Yum module which is not published.

alvagante commented 11 years ago

You are definitively right. Going to upload at least the basic modules. My problem with the Forge is that the upload procedure is still cumbersome and manual, and this has prevented my from contributing actively on it. But I know that Ken Barber and his colleagues are working on this... In a few minutes I'm going to upload the firewall, monitor, nagios, yum and icinga modules.. please let me know if you need more... (Currently I suggest to git clone recursively the whole puppet-modules-nextgen github repo and eventually cherry pick the modules you need)

codeaholics commented 11 years ago

Thanks for the quick reply. It's a shame the forge process slows things down. Your modules are excellent and being able to automate publishing (perhaps via CI) would be of great benefit to the whole community.

I'm struggling with a good workflow for incorporating 3rd party modules at the moment.

None of these provide a particularly straightforward initial deployment or upgrade story or handle dependency management. Some even include all the commits on the 3rd party module in my repo, which is horrible.

The 'puppet module' stuff looks like it should work well and solve all these problems.

Would it be easier if you hosted your own repo (see the --module-repository option of 'puppet module': http://docs.puppetlabs.com/man/module.html).

Any way, thank you for publishing those dependencies!

Keep up the good work!

On 4 Dec 2012, at 19:44, Alessandro Franceschi notifications@github.com wrote:

You are definitively right. Going to upload at least the basic modules. My problem with the Forge is that the upload procedure is still cumbersome and manual, and this has prevented my from contributing actively on it. But I know that Ken Barber and his colleagues are working on this... In a few minutes I'm going to upload the firewall, monitor, nagios, yum and icinga modules.. please let me know if you need more... (Currently I suggest to git clone recursively the whole puppet-modules-nextgen github repo and eventually cherry pick the modules you need)

— Reply to this email directly or view it on GitHub.

alvagante commented 11 years ago

Thank you very much, I'm confident that the Forge and puppet module will soon be able to integrate directly with GitHub, or eventually other source repositories, that would be a huge step forward, imho, as I suspect that many modules on the Forge are obsolete (I don't think many people keep them updated if they can't automate the upload).