Feature #33419
Feature #33329: Refactor fact parsers
Add fact parser registry
Difficulty:
Triaged:
No
Description
Since the parsers are in core. It's a good idea to move registering of parsers to a separate component.
Associated revisions
History
#1
Updated by Dominik Matoulek over 1 year ago
Updated by - Description updated (diff)
#2
Updated by The Foreman Bot over 1 year ago
Updated by - Assignee set to Dominik Matoulek
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/8762 added
#3
Updated by The Foreman Bot over 1 year ago
- Pull request https://github.com/theforeman/foreman/pull/8781 added
#4
Updated by The Foreman Bot over 1 year ago
- Fixed in Releases 3.1.0 added
#5
Updated by Dominik Matoulek over 1 year ago
- Status changed from Ready For Testing to Closed
Applied in changeset foreman|fcd63a38456375144f15d174d8945e68615e0c1d.
#6
Updated by Amit Upadhye over 1 year ago
Updated by - Category set to Facts
Fixes #33419 - Introduce Fact Parser Registry
FactParser class has two purposes in current codebase. It acts as parent
for other fact parses (PuppetFactParser, AnsibleFactParser,
RhsmFactParser...) and also as a registry for registering parsers for
given type/key. This PR introduces FactParserRegistry under
Foreman::Plugin namespace. Thanks to that, the FactParser
can takes care only for facts!