Allows for the inclusion of multiple Inspec profiles for the Effortless package, specified as directory names with scaffold_profiles variable.
Currently when running multiple Effortless Inspec packages on a node, only the latest package to send result data will have results showing in the UI for Automate. To work around this a wrapper profile can be used, but then all controls show up under a potentially monolithic profile.
These changes add the ability to include multiple profiles in a single Effortless Inspec package, each of which will have results populated to Automate as discreet profiles.
The other option right now is to use scaffolding-chef-benchmark which has two caveats:
does not support multiple profiles for Windows currently.
All additional profiles with scaffolding-chef-benchmark must be discreet Effortless Audit packages. This in itself is not an issue, but adds additional complication of maintaining multiple Effortless Audit packages and making sure that versions are all in alignment. If a customer has 10+ Effortless Audit packages and the underlying Inspec versions change or package dependencies, this could cause an issue from a dependency conflict if only one of the packages were to be rebuilt for a content update with new underlying versions. This creates a scenario where in order to update one profile safely, all packages must be rebuilt each time for every promotion to make sure there are no dependency conflicts.
Allows for the inclusion of multiple Inspec profiles for the Effortless package, specified as directory names with
scaffold_profiles
variable.Currently when running multiple Effortless Inspec packages on a node, only the latest package to send result data will have results showing in the UI for Automate. To work around this a wrapper profile can be used, but then all controls show up under a potentially monolithic profile.
These changes add the ability to include multiple profiles in a single Effortless Inspec package, each of which will have results populated to Automate as discreet profiles.
The other option right now is to use
scaffolding-chef-benchmark
which has two caveats:scaffolding-chef-benchmark
must be discreet Effortless Audit packages. This in itself is not an issue, but adds additional complication of maintaining multiple Effortless Audit packages and making sure that versions are all in alignment. If a customer has 10+ Effortless Audit packages and the underlying Inspec versions change or package dependencies, this could cause an issue from a dependency conflict if only one of the packages were to be rebuilt for a content update with new underlying versions. This creates a scenario where in order to update one profile safely, all packages must be rebuilt each time for every promotion to make sure there are no dependency conflicts.