Service Scaffolding
Creates a repository for a new-service request from your golden-path template and checks it against six production-readiness items before handing it over. Also moves older scaffolds to the current template.
How it works
- Runs when: an issue is labelled as a new-service request.
- Fills every item: CI required on main, container requests and limits, monitors and an SLO as code, a PagerDuty service, a catalog entry, and CODEOWNERS. Each value says where it came from. It never hands the team a TODO.
- Asks when it must: if a value can be neither found nor defaulted, it asks on the request and creates nothing.
- Waits for approval: creating the repository waits for platform engineering. Afterwards it reads every item back from the live systems.
- You get: a new service at six of six, or one pull request that brings an existing one there.
What it needs
- GitHub: create repositories, open pull requests
- Datadog: create monitors and SLOs
- PagerDuty: create the service