Is your feature request related to a problem? Please describe.
Currently the CACAO spec does not specify the outcome of a action step but different steps can have different defined outcomes. E.g. HTTP uses return header, return body and status code. This feature allows a playbook to define the mapping these standard outcomes into specific variables.
Describe the solution you'd like
Definition of specific outcomes per step type and a mechanism of mapping these into pre defined variables. Also these variables can have processing to them like applying jq, regex etc to them.
Describe alternatives you've considered
Direct mapping of all of these into one variable
Additional context
Results are undefined so usage of variables in playbooks by getting them is hard.
Is your feature request related to a problem? Please describe.
Currently the CACAO spec does not specify the outcome of a action step but different steps can have different defined outcomes. E.g. HTTP uses return header, return body and status code. This feature allows a playbook to define the mapping these standard outcomes into specific variables.
Describe the solution you'd like
Definition of specific outcomes per step type and a mechanism of mapping these into pre defined variables. Also these variables can have processing to them like applying jq, regex etc to them.
Describe alternatives you've considered
Direct mapping of all of these into one variable
Additional context
Results are undefined so usage of variables in playbooks by getting them is hard.