Skip to content

Consider packaging with e.g. (docker) Drydock pattern #359

Description

@openprivacy

To avoid local dependency conflicts and enable packaging that "just works" in sandbox and CI environments, consider the Drydock Pattern. We've used this pattern to create a set of compliance tools that reads templated markdown to produce an SSP. (Disclaimer: we "extended" the opencontrol schema so this is not currently compliance-masonry compatible.)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions