Samples & Templates
This section is a library of complete, schema-valid manifest templates for the most common Infrastream scenarios. Every sample is validated against the current manifest schema and mirrors the shapes used in real deployments.
Two audiences use these:
- You — copy a template, adjust the names/values, and open a pull request.
- pvot — the AI agent draws on these templates as starting points when it drafts manifests from a natural-language request, so its output follows the same conventions.
For the exhaustive, field-by-field definition of every manifest, see the Manifest Reference.
Conventions used in every sample
apiVersionis alwayslowops.manifests.v1.- Parent relationships live in
metadata, not folders. Each manifest names its parents via keys likeorganization,organizational-unit,environment,project,release-track,application-set,github-connection, andgithub-repository. The engine discovers files anywhere in the repo and resolves the graph from these keys. specis your desired state;computedis read-only and populated by the engine — never author it.- A comment at the top of each block shows the conventional file path in the repository.
Recommended repository layout
manifests/
├── organization.yaml
├── organization-user/ · organization-user-group/
├── github-connection/<conn>/{<conn>.yaml, github-repository/<repo>/{<repo>.yaml, build-definition/<repo>.yaml}}
├── artifact-registry/ · external-registry/<reg>/trusted-repository/
└── organizational-unit/<ou>/
├── <ou>.yaml
├── environment/<env>/{<env>.yaml, project/<proj>/{<proj>.yaml, database/ bucket/ ... , deployment-config/<app>.yaml}}
└── release-track/<track>/{<track>.yaml, application-set/<set>/{<set>.yaml, application/<app>.yaml}}
The pages
- Organization Foundation — Organization, OU, Environment, Project, ReleaseTrack.
- Source & Build — GithubConnection, GithubRepository, BuildDefinition, ArtifactRegistry.
- Registries & Trust — ExternalRegistry, TrustedRepository.
- Application Delivery — ApplicationSet, Application, ExternalApplication, DeploymentConfig.
- Database & Access — Database (AlloyDB) and application access grants.
- Storage, Messaging, Cache & Secrets — Bucket, PubSub, Redis, Secret.
- Access & Identity — OrganizationUser, OrganizationUserGroup, permissions.
- Full Project Bootstrap — a minimal end-to-end set that deploys one service with a database.