ores.doc.modeling.service_registry
Catalogue of ORE Studio backend services and fleet processes. Each top-level
heading is one entry with two independent, both-optional aspects: DB access
(connection variables, IAM role, and the DML/select/execute prefixes the SQL
GRANT generator uses to build per-service GRANT statements – only for
entries with their own NATS-domain-service role) and deployment (replica
count, enabled flag, startup dependencies, and per-service CLI flags that
compass systemd generate uses to render one concrete unit per service).
Every entry needs the deployment aspect; not every entry needs the DB-access
one.
See the Template variable reference and Codegen input org-file schema reference for the complete schema.
Template
The full template source. Edit here and re-tangle with
compass build --direct tangle_codegen_templates to regenerate
library/templates/doc_service_registry.org.mustache.
{{! GENERATED FILE — tangled from projects/ores.codegen/library/templates/doc.org. Edit the org source. }}
:PROPERTIES:
:ID: {{id}}
:END:
#+title: {{title}}
#+description: {{description}}
#+type: ores.codegen.service_registry
#+filetags: {{filetags}}
#+created: {{date}}
#+updated: {{date}}
(One paragraph: what services are catalogued here and how this file is consumed.)
* ores.example.service
:PROPERTIES:
:psql_var: example_service
:env_key: EXAMPLE_SERVICE
:iam_role: ExampleService
:description: Example Service
:email: example_service@system.ores
:replicas: 1
:enabled: true
:depends_on: ores.iam.service
:END:
** DML prefixes
- ores_example_
** Extra args
- --example-flag value