Skip to content

Create a threat model for code flow to internal/public VMR-lite's #11981

@premun

Description

@premun

Context

We need to make sure the code flows from the right branches and is not pushed to the wrong branches (e.g. internal/release doesn't end up in public VMR).

Goal

  • Prepare a documentation with a diagram for the code flow and exercise few paths (branching, CVE, ..).
  • Propose guards that will make sure we don't push where we should not.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions