Create a service
Scaffold a new service from a golden path, wired and guarded from the first commit.
A new service should start inside the guardrails, not outside them. Golden paths make that the default: you fill in a few details and get a repository already wired to your CI, your scanners, and a deploy target.
Scaffold from a golden path
From the Catalog, choose to create a new service and pick a golden path. A golden path is a template your platform team authored for a particular kind of service. You provide the basics, such as a name, an owner, and the target to deploy to.
When you submit, the platform scaffolds the service for you. Depending on the golden path, that typically includes:
- A repository in your source control, with a starter project and a pipeline definition.
- The pipeline wired to your CI, with security scans as steps and policy gates in place.
- A deploy target configured, so the service has somewhere to ship.
- The service registered in the catalog, with an owner and a scorecard.
Read the scorecard
Every service in the catalog carries a scorecard: a running read on its health across things like security findings, delivery, and ownership. The scorecard is how you tell, at a glance, whether a service is in good shape, and it is the same signal the platform uses when it decides whether a change is allowed to ship.
Why scaffold instead of copy
Copying an old repo carries its old mistakes forward. A golden path carries the current right answer forward: when the platform team improves the template, new services get the improvement, and existing ones can be nudged toward it through the scorecard rather than a migration project.
Next
With a service scaffolded, bring the tools it uses under governance: Connect a tool.