In Foreman 1.22 the Proxy registration protocol changed. This blog takes a look at how it was, how it’ll be and why this is an improvement.
This is a companion discussion topic for the original entry at
Are there already some functions to access the providers, exposed settings and capabilities in Foreman? My idea would be to expose some settings in the Monitoring Smart Proxy and show them in the Service overview for the Smart proxy in Foreman.
There are 2 methods on the SmartProxy model:
self.smart_proxy_features.find_by(:feature_id => Feature.find_by(:name => feature)).try(:capabilities)
def setting(feature, setting)
self.smart_proxy_features.find_by(:feature_id => Feature.find_by(:name => feature)).try(:settings).try(:, setting)
For some examples, we can look at the Puppet module which exposes the the
default_settings :puppet_ssl_ca => '/var/lib/puppet/ssl/certs/ca.pem', :api_timeout => 30
plugin :puppet_proxy_puppet_api, ::Proxy::VERSION
load_validators :url => ::Proxy::Puppet::Validators::UrlValidator
validate :puppet_url, :url => true
validate_readable :puppet_ssl_ca, :puppet_ssl_cert, :puppet_ssl_key
I’ve opened a PR to use this:
02:58PM - 26 Feb 19 UTC
When the proxy exposes the puppet_url setting for the Puppet or Puppet CA featur
Other examples are in the smart_proxy_pulp plugin:
These are used in
I’ll gladly help with patches to the monitoring.