Cheat notes · Module 04 · What the platform offers
Golden paths: the supported way, not the only way
A five-minute review for when you have done this module and want it back in your head. Open the full module for the steps and the lab, or the full text to print.
The idea
A golden path is the opinionated and supported way to do one job end to end. It is optional, so it must be the easiest way; it has an escape hatch, and it paves only with what exists.
Remember
- Spotify (2020): "the 'opinionated and supported' path to 'build something'".
optional: trueand anescapeHatch(ruleG3);support(G4).- Every step's capability must exist and not be
planned(G2). - Mandatory rules are guardrails, enforced by policy, not by the path.
- A template is one step of a path, not the path.
Pitfalls
- A step on a planned capability fails
G2: the path promises what does not exist. - A mandatory path is a mandate; teams leave it silently or fight it.
- An eleven-step path that covers every case gets used by nobody.
golden-paths/new-service.yaml (part)
optional: true
escapeHatch: >-
A team that needs something else builds it themselves, writes an ADR, and owns its pipeline and on-call.
support: "#platform-help, answered within one working day"
steps:
- t: Create the repository from the template
capability: repo-template
Test yourself
Answer in your head first, then open the answer.
What should a team do when the path does not fit?
Follow the escape hatch: take on that part, write down why, tell the platform team.
Path or guardrail: "no prod deploy without approval"?
A guardrail: it applies on and off the path.
When does a step for a new capability go into the path?
In the same change that marks the capability offered or beta.
Where module 04 leaves you: golden-paths/new-service.yaml passes the check: six steps on offered capabilities, optional: true, an escape hatch, a support channel, and for: [humans].