Actions
Bug #23530
closedforeman_openscap should not require puppet classes be imported
Status:
Duplicate
Priority:
High
Assignee:
-
Target version:
-
Description
I just installed tfm-rubygem-foreman_openscap-0.7.13-1.fm1_15.el7.noarch on Foreman 1.15.6 and discovered I have to import Puppet classes in order to start adding content. I don't use that feature of Foreman, I define all classes via roles/profiles and Hiera. It would be handy if this class requirement was removed or made optional.
When I try to add a new policy after giving it a name and hitting "Next" I get this:
Unable to save
Puppet class foreman_scap_client does not have policies class parameter.
As a work around I'm importing classes but I'd rather not pollute my instance of Foreman with Puppet classes when we don't want to support classes getting added via Foreman.
Updated by Ondřej Pražák over 5 years ago
- Is duplicate of Feature #23950: Satellite should support SCAP reports without the need of puppet installed on hosts added
Actions