Bug 2223507 - [RFE] Add variable in Ansible Role and puppet module to customizing the path for oscap argument " --local-files"
Summary: [RFE] Add variable in Ansible Role and puppet module to customizing the path ...
Keywords:
Status: NEW
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: SCAP Plugin
Version: 6.13.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-07-18 05:26 UTC by Satyajit Das
Modified: 2023-07-19 00:30 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SAT-19020 0 None None None 2023-07-18 11:33:14 UTC

Description Satyajit Das 2023-07-18 05:26:33 UTC
1. Proposed title of this feature request :

Add variable in Ansible Role and puppet module to customizing the path for oscap argument " --local-files" 


2. What is the nature and description of the request? 


Currently, there's no option to customizing the path for oscap argument " --local-files" 

For example running a compliance scan "/usr/bin/foreman_scap_client 2" by default the /root folder is checked for the file 'security-data-oval-com.redhat.rhsa-RHEL8.xml.bz-2', instead of the /root  folder,  variable in Ansible Role and puppet module should be made available to customizing the path for oscap argument " --local-files" 

3. Why does the customer need this? (List the business requirements here)  


Customer would like to customize the path based on his env.


4. Is there already an existing RFE upstream or in Red Hat Bugzilla? 
No
  
5. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?  
No
  
6. Is the sales team involved in this request and do they have any additional input?  
No 

7. List any affected packages or components.
N/A  
  
8. Would the customer be able to assist in testing this functionality if implemented?
Yes


Note You need to log in before you can comment on or make changes to this bug.