Bug #7833
closed
Deploy foreman_url setting for proxy configuration
Added by Lukas Zapletal over 10 years ago.
Updated about 10 years ago.
Description
We need to deploy this setting in the proxy YAML config file:
:foreman_url: https://FQDN
ABRT 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.
- Category set to Foreman modules
- Priority changed from High to Normal
ABRT proxy plugin is the first plugin that relies on this.
I believe the chef plugin needs this as well.
- Has duplicate Bug #8373: Set :foreman_url in /etc/foreman-proxy/settings.yml added
- 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?
- Related to Bug #8372: Make puppet ssl certificate+key that is used to authenticate against foreman available to the smart-proxy added
Then it's just a matter of using it in the template :)
- Status changed from New to Closed
- % Done changed from 0 to 100
- Bugzilla link set to 1180666
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by Anonymous 
Updated by