What problem does it solve?
Managing versioned security profiles in the ComplianceAsCode repository requires manually creating paired profile files, keeping extends references in sync, and deprecating old versions, which is error-prone when done by hand across multiple products.
Core Features & Use Cases
- Create versioned profile pairs: Generates a versioned profile (e.g., cis-v1-7-0.profile) with selections and metadata plus an unversioned profile that extends it, for one or more products.
- Update profile versions: Bumps an existing profile to a new version by copying selections, deprecating the previous versioned profile, and repointing the unversioned extends reference.
- Control file validation: Checks that matching control files under controls/ list all target products before profile creation.
- Use Case: When a new CIS benchmark version 1.8.0 is released for OpenShift, run the update action to create cis-v1-8-0.profile, deprecate cis-v1-7-0.profile, and repoint cis.profile in one guided flow.
Quick Start
Ask the assistant to create a new versioned profile, for example by saying: create a cis profile for ocp4 at version 1.7.0.