Skip to content

Commit

Permalink
Clarify that foreman_scap_client is included in client repo
Browse files Browse the repository at this point in the history
  • Loading branch information
aneta-petrova authored Jan 28, 2025
1 parent 8b5b298 commit 41699f0
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion plugins/foreman_openscap/1.0/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -126,7 +126,7 @@ Edit ```/etc/foreman-proxy/settings.d/openscap.yml``` with the appropriate setti
Workflow with Puppet and Ansible is similar. In the first step, you install appropriate package and import module or role which takes care of the client deployment. Foreman overrides parameters/variables for port, server and policies behind the scenes to make sure appropriate configuration is available to the client. When configuration is applied to host, foreman_scap_client is installed, client config is written to ```/etc/foreman_scap_client/config.yaml``` and a cron that will upload reports based on configuration of each policy is created.

It is important to make sure *foreman_scap_client* package is available to your client system. Foreman plugins repo can be optionally enabled using the appropriate parameters/variables. The repo is disabled by default as users may prefer to use their own mirror.
It is important to make sure the *rubygem-foreman_scap_client* package is available on your client system. The package is included in the [Foreman client repository](https://yum.theforeman.org/client/3.13/el9/x86_64/).

### 2.3.1 Puppet

Expand Down

0 comments on commit 41699f0

Please sign in to comment.