S-18b, second of the S-18 (#19) split (after S-18a #139/#142). Stands up the upstream Maykin Objecten API in the compose stack and wires it to the Objecttypen API — the authoritative object store the ACL will write register records to (S-19).
Compose (main + local): objecten-db (PostGIS — objects carry geometry), objecten-redis, objecten-init (RUN_SETUP_CONFIG → migrate + provision token + register the Objecttypen service), objecten web (health on /admin/, host :8021). Verbatim upstream image maykinmedia/objects-api pinned to 3.4.0 (nearest release to objecttypes-api 3.4.2; the two speak over the stable Objecttypes API v2).
Seed: infra/seed-config.sh objecten streams infra/objecten/setup_configuration/data.yaml into the external rr-objecten-config volume — same pattern as S-18a. The data.yaml (1) registers Objecttypen as a trusted zgw_consumers service (api_type: orc, api-key auth with the S-18a dev token) so an object can reference its objecttype, and (2) provisions a dev static API token so peers (the ACL, S-19) can write objects.
Wiring: added to WAIT_SVCS, CFG_VOLS, the SEED invocations, seed-config.sh, and the CI log-dump. objecten-init waits on objecttypen being healthy so the service registration is meaningful end to end.
Smoke: verify-objecten (infra/run-objecten-check.sh + objecten-check.py) asserts unauth → 401, token → 200 on /api/v2/objects; added as a verify-stack step + a row in the #136 check-summary table.
Verified locally (end to end, real compose)
Seeded + brought up the real infra/docker-compose.yml objecten chain (pulls in objecttypen via depends_on): objecten-init ran setup_configuration — token_configuration_successand "Successfully executed step: Configuration to connect with external services" — the web reached healthy, and make verify-objecten → "OK — no-auth 401, token 200". Confirmed the registered service via the Objecten django shell:
## What & why
S-18b, second of the S-18 (#19) split (after S-18a #139/#142). Stands up the upstream Maykin **Objecten API** in the compose stack and wires it to the Objecttypen API — the authoritative object store the ACL will write register records to (S-19).
Closes #140
### What
- **Compose** (main + local): `objecten-db` (**PostGIS** — objects carry geometry), `objecten-redis`, `objecten-init` (RUN_SETUP_CONFIG → migrate + provision token + register the Objecttypen service), `objecten` web (health on `/admin/`, host `:8021`). Verbatim upstream image `maykinmedia/objects-api` pinned to `3.4.0` (nearest release to objecttypes-api `3.4.2`; the two speak over the stable Objecttypes API v2).
- **Seed**: `infra/seed-config.sh objecten` streams `infra/objecten/setup_configuration/data.yaml` into the external `rr-objecten-config` volume — same pattern as S-18a. The data.yaml (1) registers **Objecttypen** as a trusted `zgw_consumers` service (`api_type: orc`, api-key auth with the S-18a dev token) so an object can reference its objecttype, and (2) provisions a dev **static API token** so peers (the ACL, S-19) can write objects.
- **Wiring**: added to `WAIT_SVCS`, `CFG_VOLS`, the `SEED` invocations, `seed-config.sh`, and the CI log-dump. `objecten-init` waits on `objecttypen` being healthy so the service registration is meaningful end to end.
- **Smoke**: `verify-objecten` (`infra/run-objecten-check.sh` + `objecten-check.py`) asserts unauth → 401, token → 200 on `/api/v2/objects`; added as a verify-stack step + a row in the #136 check-summary table.
## Verified locally (end to end, real compose)
Seeded + brought up the real `infra/docker-compose.yml` objecten chain (pulls in objecttypen via `depends_on`): `objecten-init` ran setup_configuration — `token_configuration_success` **and** "Successfully executed step: Configuration to connect with external services" — the web reached healthy, and `make verify-objecten` → **"OK — no-auth 401, token 200"**. Confirmed the registered service via the Objecten django shell:
```
objecttypen | orc | http://objecttypen:8000/api/v2/ | api_key
```
YAML (both compose files + ci.yaml) + shell + python all validated; `docker compose config` clean on both files.
## Definition of Done
- [x] Failing smoke committed first (`test(infra): …`, "no running objecten container"); implementation makes it pass.
- [x] Conventional Commits referencing #140.
- [ ] CI green (verify-stack objecten step).
- [x] `docker compose up` reaches health (objecten healthy on first poll locally).
- [x] Demo note in `docs/demo-script.md`.
- [x] Closed by the merging PR (`closes #140`).
No new ADR: follows the established verbatim-image + seed-config CG-module pattern (S-18a/ADR-0023-era).
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Fails against the current stack (no objecten service yet) with a clear
"no running objecten container" message. Green comes with the compose
service + seeded setup_configuration in the next commit.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Stands up the upstream Maykin Objecten API in the stack — own PostGIS DB
+ redis, an -init that runs setup_configuration from the external config
volume (migrate + provision a static token + register the Objecttypen API
as a trusted service), and a health-checked web on host :8021. Objecten's
setup_configuration registers Objecttypen (api_type orc, api_key auth with
the S-18a dev token) so an object can reference its objecttype.
Same verbatim-image + seed-config pattern as S-18a. Wired into WAIT_SVCS,
CFG_VOLS, the SEED invocations, seed-config.sh, and the CI log-dump. Pinned
objects-api 3.4.0 (nearest release to objecttypes-api 3.4.2).
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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-18b, second of the S-18 (#19) split (after S-18a #139/#142). Stands up the upstream Maykin Objecten API in the compose stack and wires it to the Objecttypen API — the authoritative object store the ACL will write register records to (S-19).
Closes #140
What
objecten-db(PostGIS — objects carry geometry),objecten-redis,objecten-init(RUN_SETUP_CONFIG → migrate + provision token + register the Objecttypen service),objectenweb (health on/admin/, host:8021). Verbatim upstream imagemaykinmedia/objects-apipinned to3.4.0(nearest release to objecttypes-api3.4.2; the two speak over the stable Objecttypes API v2).infra/seed-config.sh objectenstreamsinfra/objecten/setup_configuration/data.yamlinto the externalrr-objecten-configvolume — same pattern as S-18a. The data.yaml (1) registers Objecttypen as a trustedzgw_consumersservice (api_type: orc, api-key auth with the S-18a dev token) so an object can reference its objecttype, and (2) provisions a dev static API token so peers (the ACL, S-19) can write objects.WAIT_SVCS,CFG_VOLS, theSEEDinvocations,seed-config.sh, and the CI log-dump.objecten-initwaits onobjecttypenbeing healthy so the service registration is meaningful end to end.verify-objecten(infra/run-objecten-check.sh+objecten-check.py) asserts unauth → 401, token → 200 on/api/v2/objects; added as a verify-stack step + a row in the #136 check-summary table.Verified locally (end to end, real compose)
Seeded + brought up the real
infra/docker-compose.ymlobjecten chain (pulls in objecttypen viadepends_on):objecten-initran setup_configuration —token_configuration_successand "Successfully executed step: Configuration to connect with external services" — the web reached healthy, andmake verify-objecten→ "OK — no-auth 401, token 200". Confirmed the registered service via the Objecten django shell:YAML (both compose files + ci.yaml) + shell + python all validated;
docker compose configclean on both files.Definition of Done
test(infra): …, "no running objecten container"); implementation makes it pass.docker compose upreaches health (objecten healthy on first poll locally).docs/demo-script.md.closes #140).No new ADR: follows the established verbatim-image + seed-config CG-module pattern (S-18a/ADR-0023-era).
🤖 Generated with Claude Code