summaryrefslogtreecommitdiff
path: root/manifests/module.pp
AgeCommit message (Collapse)Author
2015-05-14Fix module management on Debian, closes #7Jerome Charaoui
Manage files and symlinks directly instead of using a2enmod/a2dismod, which are interactive utilities anyway.
2012-07-18make $package_name behave appropriately with apache::debian::moduleGabriel Filion
the default value for package_name in apache::debian::module is 'absent'. Using an empty value makes apache::module's default value break, saying that the package '' (nothing) cannot be found. Signed-off-by: Gabriel Filion <lelutin@gmail.com>
2012-07-18add 2.6.x compatibility to the default value of $moduleGabriel Filion
using $name in a default value doesn't work in 2.6.x, we need to verify the argument's value inside the manifests. Signed-off-by: Gabriel Filion <lelutin@gmail.com>
2012-07-18Move oddly-placed closing bracketGabriel Filion
usually, closing a curly bracket on the same line as the code is done when it is opened on the same line, too. here we'd rather align it to the "default:" to make the code easier to read. Signed-off-by: Gabriel Filion <lelutin@gmail.com>
2012-07-16change the class to a define and pass $name to $module by defaultMicah Anderson
2012-07-16single-quoting style diffMicah Anderson
2012-07-08there is a apache::centos::module, apache::gentoo::module, and ↵Micah Anderson
apache::debian::module which means you have to specify the operating system in the class that you called for deployment of the module. so I abstracted that by creating the class apache::module in manifests/module.pp which just did an fact check and then depending on the result, called the correct class for module deployment