-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use foreman apache configs to unblock Pulp 3 #225
Conversation
@ekohl general thoughts on this overall approach? It is related to this change theforeman/forklift#1105 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In my local dev env I have a WIP patch that attempted to do the same thing but it looks like I never finished that. It was certainly my intention to use it this way. I also thought about refactoring the class slightly in puppet-foreman to make it easier to consume. We can do that by not having defaults inheriting from foreman
but rather working defaults. Then in the foreman::config
class we explicitly set the parameters.
I'd like to see a version that uses theforeman/puppet-foreman#800 because it should be simpler. |
56b9b5e
to
3aba7cf
Compare
3aba7cf
to
df136e6
Compare
df136e6
to
b89fe3a
Compare
All cleaned up and ready to party |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IMHO it makes sense to further update the module in later PRs to isolate more parts
@@ -178,37 +178,9 @@ | |||
require => Class['katello_devel::database'], | |||
} | |||
|
|||
User<|title == $user|>{groups +> 'qpidd'} | |||
|
|||
# TODO: Use katello::pulp |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yay for cleaning up my TODOs
This module had declared it's own vhost using a similar naming convention and directory structure as Foreman's. This causes a conflict when pulpcore is enabled since pulpcore relies on adding fragments to Foreman's vhost declaration specifically around the use of
05-foreman-ssl.d
. To solve this, and bring greater continuity I have attempted to declare theforeman::config::apache
class and re-use it here.