Revenue deployment

Revenue contains the catalog and pricing domains. Its service skeleton and deployment configuration are committed. Dev database and identity credentials are provisioned; the first deployment is pending pipeline resource authorization and merge.

Pipeline registration

Azure pipeline 110, [service] revenue is registered in the service folder, with develop as its default branch and services/revenue/.azure/azure-pipelines.yml as its YAML path. It follows the existing service pipeline layout and deploys the revenue-api Helm release to dev/us/core.

The definition was registered disabled, without queuing a run. Merging this change leaves it disabled. Azure DevOps stores the registration and queue status separately from Git; committing a pipeline YAML file does not register a pipeline.

The DevOps deployments page lists installed Helm releases. Registration alone does not make revenue appear there.

Before enabling deployment

The required environment settings and identity prerequisites are maintained in services/revenue/.azure/env/readme.md↗. Complete those prerequisites before enabling pipeline 110:

1. Verify revenue's own database and its environment-specific encrypted secrets. Dev provisioning was completed on 2026-09-25. Follow docs/devops/deploying-a-service.md↗; do not copy another service's secrets.
2. The dev reader client, secret mapping, system principal and principal-reader grant are provisioned. The encrypted mapping is included with the client registration. Revenue uses the internal Identity service with an explicit dev-only HTTP exception; its token endpoint remains HTTPS. The environment readme gives the required order.
3. Have an Azure DevOps administrator authorize pipeline 110 for variable groups internals and externals and service connections dev-flow and dev-acr. The provisioning account received HTTP 401 when authorizing the variable groups and could not list the service connections.
4. After the PR is merged and provisioning is complete, enable pipeline 110 and manually run it on develop. Subsequent changes under services/revenue on develop trigger dev deployment.
5. Verify the migration hook, ready pods and the revenue-api Helm release in dev/us/core. Add revenue to DEPLOYED_SERVICES only when its public API is ready for inclusion in the merged platform specification.

The existing production stage is selected by main; first-deploy preparation here is for dev only. No production deployment or access grant is part of registration.