Skip to content

Optimize SecOps to combine into single Sec Blocks when possible #49

@jeronstone

Description

@jeronstone

SecOps with like information (same sec ctx, params, etc.) but with different targets should be combined into one Security block. At the moment, the backend SC creates one new Security block for each new Sec Op.

Sec Blocks as defined in the backend can currently support more than 1 target, but the default processing of SecOps does not optimize to create single Sec Blocks in cases where it can - This would be a good optimization.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    Status

    Todo

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions