Closed hsnodgrass closed 4 weeks ago
Rolling out something like this needs to happen in the task spec and have a path forward for all task runners (most notably PE).
Rolling out something like this needs to happen in the task spec and have a path forward for all task runners (most notably PE).
Is this something I can help with? If so, where should I look?
@donoghuc I've updated this PR based on the discussion in #159
@donoghuc anything else need to be done on this before it gets merged?
nope, looks good to me. I think we've waited long enough to allow for other opinions.
This commit adds the
identifiers
field to Bolt task metadata. A brief description of why anidentifiers
field would be useful is included in thetasks/README.md
update. A more concrete example is writing Bolt tasks to help with security compliance. In order to map tasks to compliance rules, you either need to name your task after a rule or use comments in the implementation script. With the newidentifiers
field, you could add a keys underidentifiers
showing details about the security controls implemented.This PR addresses issue #159