A remediation snippet is supposed to be self-contained. We have a legacy functionality for shared bash functions for bash remediations, but all new remediation families should jinja macros in cases when remediation code is shared across multiple rules, and you are thinking about reducing remediation code duplication.

Check out e.g. https://github.com/ComplianceAsCode/content/blob/master/docs/manual/developer_guide.adoc#722-bash to learn more about writing bash remediations.

On 12. 02. 20 23:31, Trevor Vaughan wrote:
I was looking at updating some of these but do they have to be 100% self contained?

Obviously, some items are quite complex and there is code to do what is required, but I'm not sure how detailed we want to go.

Thanks,

Trevor

--
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699 x788

-- This account not approved for unencrypted proprietary information --

_______________________________________________
scap-security-guide mailing list -- scap-security-guide@lists.fedorahosted.org
To unsubscribe send an email to scap-security-guide-leave@lists.fedorahosted.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedorahosted.org/archives/list/scap-security-guide@lists.fedorahosted.org