You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
RabbitMQ service: declaration and validation (S-023-1, S-023-2, S-023-18) #505
Builds part of spec S-023, docs/specs/023-rabbitmq-service.md: the acceptance criteria below. Each needs a test that names its id (test_s023_<k>_..., or a proves: S-023-1 comment line).
Scope: the serviceKind: rabbitmq declaration in the schema and the SDK (the supported-series table with each series' end of community support and Erlang range), every refusal and warning under the spec's Validation, and the rendered inventory. No role yet.
S-023-1: A project with three Server resources, their baselines, and the declaration above passes cloudfall config validate with exit 0, and cloudfall-engine inventory render carries the service with its three nodes, its virtual host and no password value
S-023-2: For the project in config/examples without a RabbitMQ service, the rendered inventory is byte-identical before and after the change
S-023-18: Each refusal listed under Validation fails cloudfall config validate with CONFIG_INVALID and its code; version: 4.2.9 and version: 4.5.0 each fail with service_rabbitmq_version; nodes of two servers fails with service_rabbitmq_nodes; a version of a series within 90 days of its end of support validates with the warning RABBITMQ_VERSION_ENDING naming the date; one node in a production environment validates with RABBITMQ_SINGLE_NODE
Builds S-023-1, S-023-2 and S-023-18 of spec 023 (docs/specs/023-rabbitmq-service.md, approved in #500), for #502. The plan:
serviceKind: rabbitmq in config/schemas/v1/service.schema.json and the SDK, with the supported-series table (each series' end of community support and its Erlang range)
Every refusal and warning under the spec's Validation, with their codes (service_rabbitmq_version, service_rabbitmq_nodes, RABBITMQ_VERSION_ENDING, RABBITMQ_SINGLE_NODE, and the rest)
The rendered inventory carries the service, its nodes and virtual hosts, and never a password value; the example project's inventory stays byte-identical
The declaration is in #519: serviceKind: rabbitmq in the schema and the SDK, the supported-series table (4.3 and 4.4 with their end of community support), every refusal and warning under the spec's Validation with its code, and the rendered inventory carrying each node's service with passwordRef and never a password. The example project renders byte-identical (S-023-2). Readings of the spec it took are in the decided comment on the PR. This issue closes when #519 merges.
Activity
shipmill-romamo commentedon Nov 17, 2026
Triage: implement. Serves: G-1, G-3.
Builds S-023-1, S-023-2 and S-023-18 of spec 023 (
docs/specs/023-rabbitmq-service.md, approved in #500), for #502. The plan:serviceKind: rabbitmqinconfig/schemas/v1/service.schema.jsonand the SDK, with the supported-series table (each series' end of community support and its Erlang range)service_rabbitmq_version,service_rabbitmq_nodes,RABBITMQ_VERSION_ENDING,RABBITMQ_SINGLE_NODE, and the rest)It has no dependency, so it starts now. I'll link the PR here.
shipmill-romamo commentedon Nov 17, 2026
The declaration is in #519:
serviceKind: rabbitmqin the schema and the SDK, the supported-series table (4.3 and 4.4 with their end of community support), every refusal and warning under the spec's Validation with its code, and the rendered inventory carrying each node's service withpasswordRefand never a password. The example project renders byte-identical (S-023-2). Readings of the spec it took are in the decided comment on the PR. This issue closes when #519 merges.