There are a few errors and omissions in the README.md file:
foreman_scap_client_server must not contain the https:// prefix . It is incorrect in the sample section
It is not clear if content_path refers to the path on the client or the server
profile_id should be documented. It is actually the suffix of the profile you want to use (e.g. minimal, standard, or whatever else is available in the SCAP content file).
download_path should be documented. It will not always be the path given in the sample (the number in that path actually is the ID number of the policy on the server).
Also confusing that there are two different policy ids involved. The id field refers to the local ID, which will become an entry in the client-side config.yaml file, and an argument to the foreman_scap_client tool. The download_path also includes a policy ID, but this is a server-side policy ID, which may or may not have the same value.
There are a few errors and omissions in the README.md file:
Also confusing that there are two different policy ids involved. The id field refers to the local ID, which will become an entry in the client-side config.yaml file, and an argument to the foreman_scap_client tool. The download_path also includes a policy ID, but this is a server-side policy ID, which may or may not have the same value.
This fact should be better explained.