Manage HTTP config with apache module
The apache configuration is currently unmanaged, only deployed through the ipa-server-common package.
I would like to activate the apache::mod::status
config on the host, but there is conflict with the Service['httpd']
:
Duplicate declaration: Service[httpd] is already declared at (file: /etc/puppetlabs/code/environments/dev/modules/freeipa/manifests/install/server.pp, line: 112); cannot redeclare (file: /etc/puppetlabs/code/environments/dev/modules/apache/manifests/service.pp, line: 28) (file: /etc/puppetlabs/code/environments/dev/modules/apache/manifests/service.pp, line: 28, column: 5) on node XXX
Even if this duplicate declaration is resolved, the apache module would erase any configuration defined in /etc/httpd/conf.d/
by the package. I think this FreeIPA module should manage the apache vhosts. What do you think?
The two ways I see of solving this problem:
1- Do not add the apache config management in this module, only add an boolean option to define or not the Service['httpd']
in the FreeIPA module. This way, the user should manage his own apache config within his own profiles. The changes to this module would be minimal, but the work to define the apache files would have to be duplicated by the users.
2- Managing the apache config through the apache
module. It would require more maintenance on this module when upstream changes their configurations.
I won’t submit a PR about this problem right now, but I’ll put this in my backlog. Please comment on this idea, which way you think it should go.