Documentation
¶
Overview ¶
Command tally-reporting-admin provisions and revokes the Reporting API's credentials and registers its virtual projects.
The HTTP contract has no credential endpoints: a credential is issued by an operator who already holds database access, not over the API that credential opens. The CLI therefore works on the reporting database directly, through the same TALLY_REPORTING_DB_URL the server reads. On the dev cluster that connection goes through the Gateway's postgres listener.
It is also the only thing that runs DDL. Its migrate subcommand applies the embedded goose chain, migrate-status reports which of it a database carries, and migrate-down-to runs the chain's down migrations. The server migrates nothing at startup, so a schema change stays an operator's decision rather than a side effect of a pod restart.
A new token is printed once, alone on stdout, so it can be redirected into a file or a secret. The database receives its sha256 digest and never the token itself.
create-meta-project and create-partner register the virtual projects of decision D1 (roadmap/05-phase-5-commercial-pricing.md): the (meta, meta, id) and the (partner, partner, id) row. Both go through the same projects.Register the API's registration goes through and are audited as admin-cli. The new id is printed alone on stdout, so a command substitution passes it as the target_id of a relation.
The normative specification is roadmap/01-phase-1-core-platform-openstack.md, WP 1.4.
Source Files