Feature #25614
Support exposing capabilities and settings
Description
On a smart proxy feature listing, we can only get a set of named features, but features can't have optional functionality or provide any other information to the foreman server.
Related issues
Associated revisions
Refs #25614 - Fix typo in a comment
Refs #25614 - Add integration tests for capabilities
Co-Authored-By: Tomer Brisker <tbrisker@gmail.com>
Refs #25614 - Always expose the provider setting
Refs #25614 - Expose settings from the correct layer
Before this change every expose_setting would only be read from the
plugin config.
This changes makes sure that a provider can expose settings from its own
config file. For example, puppetca exposes from puppetca.yml and
puppetca_http_api exposes from puppetca_http_api.yml.
History
#1
Updated by The Foreman Bot over 4 years ago
Updated by - Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/smart-proxy/pull/625 added
#2
Updated by Justin Sherrill over 4 years ago
Updated by - Related to Feature #25642: Support Smart Proxy v2 features api added
#3
Updated by Anonymous about 4 years ago
- Status changed from Ready For Testing to Closed
Applied in changeset 8ed192be67a01ebdf39a66194cf252d20cc1f2c8.
#4
Updated by The Foreman Bot about 4 years ago
- Pull request https://github.com/theforeman/smart-proxy/pull/636 added
#5
Updated by The Foreman Bot about 4 years ago
- Pull request https://github.com/theforeman/smart-proxy/pull/640 added
#6
Updated by The Foreman Bot about 4 years ago
- Pull request https://github.com/theforeman/smart-proxy/pull/642 added
#7
Updated by Tomer Brisker almost 4 years ago
Updated by - Fixed in Releases 1.22.0 added
#8
Updated by Ewoud Kohl van Wijngaarden over 1 year ago
Updated by - Related to Feature #11798: Standard smart proxy interface for module statuses added
Fixes #25614 - v2/features API with Capabilities and exposed settings