Skip to content

Create and use separate LavaMoat policies for each build type #12690

@rekmarks

Description

@rekmarks

We exclude code based on the build-type specified to the build system, which means that LavaMoat may (and in practice, does) generate different policies depending on the build type. Therefore, we need to store one policy for each policy, keep them up to date, and use the correct policy for every build.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type
    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