The Orun composition catalog for .NET services on Azure Container Apps.
A versioned, OCI-hosted set of execution contracts — how a .NET service is
built, containerized and deployed; how a shared library is packed; how EF Core
migrations are planned and applied; how Azure infrastructure is provisioned.
Consumed by pinning a version in a repo's intent.yaml:
compositions:
sources:
- name: stack-basalt
kind: oci
ref: oci://ghcr.io/sourceplane/stack-basalt:0.1.0
resolution:
precedence: [stack-basalt]Pin an explicit version. A bare repository reference resolves to :latest,
which lets a catalog release change a consuming repo's execution contracts
without a commit there. Bumping the tag is the deliberate upgrade step.
Sibling of stack-tectonic
(Cloudflare, Terraform, monorepo). Kept separate on purpose: a container-lane
change here cannot destabilize the Cloudflare products that pin that one.
| Type | What it does |
|---|---|
dotnet-service |
Build, test, containerize via az acr build, deploy a Container Apps revision, smoke it. Ships a canary profile that shifts traffic, soaks, then promotes. |
dotnet-package |
Restore, build, test and pack a shared library. |
ef-migrate |
EF Core migration bundles — one self-contained executable, rehearsed against a throwaway Postgres before it touches an environment. |
terraform-azure |
Terraform for Azure, authenticated by workload identity federation, publishing wiring outputs. |
A profile is a capability subset, never a second script. Each composition
has one job template declaring every capability; a profile selects from it. A
verify lane is a deploy lane with the mutating capabilities excluded, so the two
cannot drift apart. scripts/verify.sh fails the build if a profile names a
capability no job template declares — and that check is itself negative-tested,
because a structural gate that silently matches nothing is worse than no gate.
No credential is ever stored. terraform-azure and dotnet-service
authenticate by workload identity federation: the runner's OIDC token is
exchanged for an Azure access token. There is no client secret to rotate, and
the azureClientId / azureTenantId / azureSubscriptionId parameters are
identifiers, not secrets. Terraform state lives on the Orun platform
(TF_HTTP_* per job), so no storage account and no -backend-config either.
No resource id is ever committed. A service commits a config template
carrying @@wiring(<component>/<env>:<key>)@@ tokens. Verify lanes render it
from a committed fixture — offline, so PR lanes need no cloud access. Deploy
lanes render it from the wiring terraform-azure published on apply.
verify-structure fails on a committed subscription id or credential material.
dotnet-service builds with az acr build, server-side: no Docker daemon
on the runner, no registry auth dance, and the layer cache lives with the
registry. The runner uploads a build context rather than pushing layers.
Images deploy by digest, never by tag — image-build resolves the digest
after pushing and hands it to deploy-revision, so a later push to the same tag
cannot change what is running.
./scripts/verify.sh # the full catalog gate, offlineIt structurally validates every contract, enforces the profile⊆template
invariant, resolves the publish target, then packs the artifact and resolves
it back through a throwaway consumer intent — the same code path a consuming
repo runs. orun publish --dry-run alone only checks the manifest, which is no
evidence the package is loadable.
Bump metadata.version in stack.yaml, then tag v<version>. CI verifies the
catalog, creates the GitHub release, publishes the OCI package, and confirms it
is pullable.