Fixes #28711 - Serve /pulp/content over http with pulp3

[wbclark]

Adds http support for /pulp/content using foreman::config::apache::fragment

[ehelms]

I think looking at this it'd be worth splitting https://github.com/theforeman/puppet-foreman_proxy_content/blob/master/templates/pulpcore-apache.conf.erb into two pieces. One fragment for the Content app and one for the API app. Then you can create fragments for each and re-use the definitions of the Content app for http and https.

[wbclark]

I think looking at this it'd be worth splitting https://github.com/theforeman/puppet-foreman_proxy_content/blob/master/templates/pulpcore-apache.conf.erb into two pieces. One fragment for the Content app and one for the API app. Then you can create fragments for each and re-use the definitions of the Content app for http and https.

This approach seems much cleaner. Will test it.

[ekohl]

Nit on the commit message: the short summary should say what it does, not what it doesn't do. https://chris.beams.io/posts/git-commit/#imperative has a great description and also examples.

[wbclark]

Nit on the commit message: she short summary should say what it does, not what it doesn't do. https://chris.beams.io/posts/git-commit/#imperative has a great description and also examples.

Noted. I simply copied the title of the Redmine but since it's linked by the issue # already I'll instead reword it to be more useful.