Bug #7833
closed
Deploy foreman_url setting for proxy configuration
Description
We need to deploy this setting in the proxy YAML config file:
:foreman_url: https://FQDNABRT proxy plugin is the first plugin that relies on this. Since this is now supported plugin I am giving this a priority to get some attention for the next sprint planning.
Updated by Dominic Cleal over 9 years ago
- Category set to Foreman modules
- Priority changed from High to Normal
Updated by Martin Milata over 9 years ago
ABRT proxy plugin is the first plugin that relies on this.
I believe the chef plugin needs this as well.
Updated by Dominic Cleal over 9 years ago
- Has duplicate Bug #8373: Set :foreman_url in /etc/foreman-proxy/settings.yml added
Updated by Lukas Zapletal over 9 years ago
- Priority changed from Normal to High
This is now needed by discovery proxy plugin as well. Boosting priority a bit.
What is the best way to implement this please? If it's easy, let's just do it right away. Should we detect the foreman_url from fqdn?
Updated by Lukas Zapletal over 9 years ago
- Related to Bug #8372: Make puppet ssl certificate+key that is used to authenticate against foreman available to the smart-proxy added
Updated by Ewoud Kohl van Wijngaarden over 9 years ago
That is the easiest. https://github.com/theforeman/puppet-foreman/blob/master/manifests/params.pp#L5 does the same. Then users who deploy it by default at least get a sane install.
Updated by Ewoud Kohl van Wijngaarden over 9 years ago
Then it's just a matter of using it in the template :)
Updated by Anonymous over 9 years ago
- Status changed from New to Closed
- % Done changed from 0 to 100
Applied in changeset puppet-foreman_proxy|7b70805aa0199bf53d9f621912fba4604bd835d8.
Updated by