example42 / puppet-activemq Goto Github PK

Running AMQ 5.14.1 (source) on Centos 7, Puppet 4.6 without issues, unfortunately, if AMQ stops puppet does not restart AMQ, or attempt.

Removing the dir/links and init script, re-run agent - does indeed download -> install -> start

The dependencies do not have apt repos for debian/ubuntu.
I intend to fix, by using the https://github.com/example42/puppet-apt module, which already has the puppetlabs repo available.

(This issue is a placeholder for myself - if github allowed me to create issues on my fork, that's where I'd put it, but it doesn't, so..)

[root@puppet manifests]# puppet module install example42-activemq
Notice: Preparing to install into /etc/puppetlabs/code/environments/production/modules ...
Notice: Downloading from https://forgeapi.puppetlabs.com ...
Error: Could not install module 'example42-activemq' (latest)
Dependency 'example42-firewall' (v2.1.3) would overwrite /etc/puppetlabs/code/environments/production/modules/firewall
Currently, 'puppetlabs-firewall' (v1.7.1) is installed to that directory
Use puppet module install --ignore-dependencies to install only this module

furthermore, the example42-firewall module states the following:

DEPRECATION NOTICE

This module is no more actively maintained and will hardly be updated.

Please find an alternative module from other authors or consider Tiny Puppet as replacement.

If you want to maintain this module, contact Alessandro Franceschi

Error: Failed to apply catalog: Parameter source failed on File[activemq.dir]: Cannot use relative URLs '' at /etc/puppetlabs/code/environments/wip_activemq/modules/activemq/manifes
ts/init.pp:422

Maybe because of the emptystring == true ?

When 'install' is set to 'puppi', and everything else is left default, on my ubuntu server, /opt/activemq becomes a symlink to /opt and thus you can recurse though an infinite level of 'activemq' symlinks and puppet then fails to ensure the config file exists underneath that directory.

This is admittedly the first module I'm trying to install with puppi as opposed to via system packages, because I don't like the way Debian/Ubuntu packages activemq. However puppi is enabled and I haven't had any other errors with it.

Any ideas why this would be? I haven't had time to dig into the module code yet to know whether it's something in activemq or in puppi.