Operating the configuration project
Definitions gather in the configuration project. The administrator’s work is to keep that place correct.
How a change to definitions proceeds
- A change to definitions is treated like a change to code: submitted as a change, verified, and only then landed
- Before it lands, the definitions are validated against every tenant. If the configuration disagrees anywhere, it stops there
- A definition that lands takes effect for every project in the same shape
Adding a project
- A project is added by registering it in the tenant’s configuration
- Registration comes with the standard checks and gates. You do not prepare a base per project
- Which jobs run in which pipeline is decided by the project side’s specification and the configuration project’s definitions
Managing exceptions
- Exceptions (such as exclusion from a check) are given an expiry and recorded on the definition side
- When an exception’s expiry comes, it is reviewed: continue it, or end it. Exceptions without an expiry are not made
Handling secrets
- Secrets are not written into procedures or jobs. A secret that is needed is handed over by the base, in encrypted form
- Because secrets never enter the procedures, definitions can be shown as they are without leaking anything