Skip to content
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_config_entry instead of manual rake config #87

Closed
wants to merge 1 commit into from

Conversation

ekohl
Copy link
Member

@ekohl ekohl commented May 12, 2016

I should note that I haven't tested this yet, this is mostly to check if this is even a good idea. theforeman/puppet-foreman#441 also suggested that this should be part of puppet-foreman itself.

@ekohl
Copy link
Member Author

ekohl commented May 13, 2016

theforeman/puppet-foreman#442 is an alternative approach. Using that would mean simply setting the correct answers.

@ehelms
Copy link
Member

ehelms commented May 13, 2016

I can test this out with our module-pr tester in kdeploy. As for the parameters, I'd still probably learn towards this approach given we'd have to define the certs in the answers file of the installer and then they are hard-coded as opposed to this approach that will update them if anything changes.

@ekohl
Copy link
Member Author

ekohl commented May 13, 2016

The current certificate locations are already hardcoded in the katello-installer answers file. By implementing this, you reduce coupling which I think is a good thing.

@stbenjam
Copy link
Member

Closed in favor of #88

@stbenjam stbenjam closed this May 16, 2016
@ekohl ekohl deleted the use-foreman-config-entry branch May 16, 2016 17:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants