On Thursday, April 23, 2015 at 4:26:22 PM UTC-5, Wil Cooley wrote: > > I'm starting to try to use the puppet-community/rundeck module, but right > away I have run into a snag with something that have bothered me in the > past: Both the rundeck module and one of my local modules tries to manage > /etc/facter and /etc/facter/facts.d. > > I don't see anything in the code or JIRA that suggests that even w/Puppet > 4 these directories are automatically created, so it's not unreasonable > that each of us should want to ensure the directory exists, but it does > seem to step outside of the rundeck module's concerns to try to manage the > module. > > I would be satisfied enough to ignore the problem and move on if the RPM > packages at least created these directories, but they do not. > >
This is one of the classic module incompatibility patterns. The best solutions all involve factoring out management of the conflicting resources to a class that the two modules can both reference. That class *could* declare the needed resources virtually, and let other classes realize them, but I like the solution Garrett describes better. Any way around, though, you can't resolve the module incompatibility without modifying at least one of the conflicting modules. John -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/92173610-236f-4acb-acdc-130940e26169%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
