Organization of policies in the repo
We are starting to create more files to represent individual policies, to be executed by separate scheduled pipelines.
This allows us to:
- Separate concerns
- Execute individually
- Define project specific policies
To organise the structure of the repo before we start introducing specific rules for different projects, should we start splitting policies into their own project-level directories? We still want to make most rulesets generic enough that they can be executed for all projects but support the ability to define different policies and packages for each project.
Edited by Mek Stittri