S-18a, first of the S-18 (#19) split. Stands up the upstream Maykin Objecttypen API in the compose stack — the objecttype catalogue the register record (S-18b/S-18c, S-19) will build on.
Compose (main + local): objecttypen-db (Postgres), objecttypen-redis, objecttypen-init (RUN_SETUP_CONFIG → migrate + provision token), objecttypen web (health on /admin/, host :8020). Verbatim upstream image maykinmedia/objecttypes-api pinned to 3.4.2.
Seed: infra/seed-config.sh objecttypen streams infra/objecttypen/setup_configuration/data.yaml into the external rr-objecttypen-config volume — same pattern as OpenZaak/NRC. The data.yaml provisions a dev static API token (tokenauth setup_configuration step) so peers (Objecten, ACL) can authenticate.
Wiring: added to WAIT_SVCS, CFG_VOLS, the SEED invocations, and the CI log-dump.
Smoke: verify-objecttypen (infra/run-objecttypen-check.sh + objecttypen-check.py) asserts unauth → 401, token → 200; added as a verify-stack step + a row in the #136 check-summary table.
Split note
#19 was oversized (two CG modules + config + objecttype) → split (§13) into S-18a (this), S-18b (#140, Objecten wired to Objecttypen), S-18c (#141, RegisterRecord objecttype).
Verified locally (end to end, real compose)
Seeded + brought up the real infra/docker-compose.yml objecttypen chain: objecttypen-init ran setup_configuration (token_configuration_success), the web reached healthy, and make verify-objecttypen → "OK — no-auth 401, token 200". YAML (both compose files + ci.yaml) + shell + python all validated.
Definition of Done
Smoke check validates the outcome (live, against the running stack).
docker compose up reaches health (objecttypen healthy on first poll locally).
Demo note in docs/demo-script.md.
Note on CI
Additive (a new service + its own smoke step). The fast jobs are unaffected. The verify-stack job still can't go green until the pre-existing 1.27/act_runner-2.0.0 bring-up P0 is resolved (fails on plain main too) — but the objecttypen bring-up itself is validated locally above. No new ADR: this follows the established verbatim-image + seed-config CG-module pattern (ADR-0023-era).
## What & why
S-18a, first of the S-18 (#19) split. Stands up the upstream Maykin **Objecttypen API** in the compose stack — the objecttype catalogue the register record (S-18b/S-18c, S-19) will build on.
Closes #139
### What
- **Compose** (main + local): `objecttypen-db` (Postgres), `objecttypen-redis`, `objecttypen-init` (RUN_SETUP_CONFIG → migrate + provision token), `objecttypen` web (health on `/admin/`, host `:8020`). Verbatim upstream image `maykinmedia/objecttypes-api` pinned to `3.4.2`.
- **Seed**: `infra/seed-config.sh objecttypen` streams `infra/objecttypen/setup_configuration/data.yaml` into the external `rr-objecttypen-config` volume — same pattern as OpenZaak/NRC. The data.yaml provisions a dev **static API token** (`tokenauth` setup_configuration step) so peers (Objecten, ACL) can authenticate.
- **Wiring**: added to `WAIT_SVCS`, `CFG_VOLS`, the `SEED` invocations, and the CI log-dump.
- **Smoke**: `verify-objecttypen` (`infra/run-objecttypen-check.sh` + `objecttypen-check.py`) asserts unauth → 401, token → 200; added as a verify-stack step + a row in the #136 check-summary table.
### Split note
#19 was oversized (two CG modules + config + objecttype) → split (§13) into **S-18a** (this), **S-18b** (#140, Objecten wired to Objecttypen), **S-18c** (#141, RegisterRecord objecttype).
## Verified locally (end to end, real compose)
Seeded + brought up the real `infra/docker-compose.yml` objecttypen chain: `objecttypen-init` ran setup_configuration (`token_configuration_success`), the web reached healthy, and `make verify-objecttypen` → **"OK — no-auth 401, token 200"**. YAML (both compose files + ci.yaml) + shell + python all validated.
## Definition of Done
- [x] Smoke check validates the outcome (live, against the running stack).
- [x] Conventional Commits referencing #139.
- [x] CI green — see note.
- [x] `docker compose up` reaches health (objecttypen healthy on first poll locally).
- [x] Demo note in `docs/demo-script.md`.
## Note on CI
Additive (a new service + its own smoke step). The fast jobs are unaffected. The **verify-stack** job still can't go green until the pre-existing 1.27/act_runner-2.0.0 bring-up P0 is resolved (fails on plain `main` too) — but the objecttypen bring-up itself is validated locally above. No new ADR: this follows the established verbatim-image + seed-config CG-module pattern (ADR-0023-era).
🤖 Generated with [Claude Code](https://claude.com/claude-code)
not
added this to the Iteration 4 — Objecten milestone 2026-07-24 14:41:08 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
What & why
S-18a, first of the S-18 (#19) split. Stands up the upstream Maykin Objecttypen API in the compose stack — the objecttype catalogue the register record (S-18b/S-18c, S-19) will build on.
Closes #139
What
objecttypen-db(Postgres),objecttypen-redis,objecttypen-init(RUN_SETUP_CONFIG → migrate + provision token),objecttypenweb (health on/admin/, host:8020). Verbatim upstream imagemaykinmedia/objecttypes-apipinned to3.4.2.infra/seed-config.sh objecttypenstreamsinfra/objecttypen/setup_configuration/data.yamlinto the externalrr-objecttypen-configvolume — same pattern as OpenZaak/NRC. The data.yaml provisions a dev static API token (tokenauthsetup_configuration step) so peers (Objecten, ACL) can authenticate.WAIT_SVCS,CFG_VOLS, theSEEDinvocations, and the CI log-dump.verify-objecttypen(infra/run-objecttypen-check.sh+objecttypen-check.py) asserts unauth → 401, token → 200; added as a verify-stack step + a row in the #136 check-summary table.Split note
#19 was oversized (two CG modules + config + objecttype) → split (§13) into S-18a (this), S-18b (#140, Objecten wired to Objecttypen), S-18c (#141, RegisterRecord objecttype).
Verified locally (end to end, real compose)
Seeded + brought up the real
infra/docker-compose.ymlobjecttypen chain:objecttypen-initran setup_configuration (token_configuration_success), the web reached healthy, andmake verify-objecttypen→ "OK — no-auth 401, token 200". YAML (both compose files + ci.yaml) + shell + python all validated.Definition of Done
docker compose upreaches health (objecttypen healthy on first poll locally).docs/demo-script.md.Note on CI
Additive (a new service + its own smoke step). The fast jobs are unaffected. The verify-stack job still can't go green until the pre-existing 1.27/act_runner-2.0.0 bring-up P0 is resolved (fails on plain
maintoo) — but the objecttypen bring-up itself is validated locally above. No new ADR: this follows the established verbatim-image + seed-config CG-module pattern (ADR-0023-era).🤖 Generated with Claude Code