not
4a047c618c
Replaying the gateway's calls against a live Objecten + Objecttypen pair turned up two blockers CI would only have found after the fact: - Objecten rejects an objecttype it has not been configured with, and it identifies one by uuid — assigned at seed time by a one-shot that runs after Objecten's static setup_configuration. Pin the uuid on both sides instead. - Objecten notifies on every write and notifications_api_common *raises* when that config is absent, so every POST 500'd after rolling the object back. Objecten → NRC has no broker, worker, kanaal or abonnement yet, so disable notifications rather than wire a client that drops every message; S-19b turns them on for real. With both in place the full exchange verifies end to end: lookup → version → search → create → update (still one object), and a record carrying a bsn is rejected by the schema. ADR-0028 records both.
43 lines
1.8 KiB
YAML
43 lines
1.8 KiB
YAML
# Objecten API setup_configuration (S-18b). Streamed into the external rr-objecten-config volume by
|
|
# infra/seed-config.sh and applied by objecten-init (RUN_SETUP_CONFIG). Declarative + idempotent.
|
|
#
|
|
# Two things: (1) register the Objecttypen API (S-18a) as a trusted service so an object can
|
|
# reference its objecttype — authenticating with the dev static token Objecttypen provisioned; and
|
|
# (2) a dev static token so peers (the ACL, S-19) can write objects here. Dev-only, not for prod.
|
|
|
|
# (1) Trust the Objecttypen API. `orc` = overige RESTful component (how zgw_consumers classifies the
|
|
# Objecttypen API). The RegisterRecord objecttype (S-18c) will reference an objecttype under this
|
|
# service by uuid.
|
|
zgw_consumers_config_enable: true
|
|
zgw_consumers:
|
|
services:
|
|
- identifier: objecttypen
|
|
label: Objecttypen API
|
|
api_type: orc
|
|
api_root: http://objecttypen:8000/api/v2/
|
|
auth_type: api_key
|
|
header_key: Authorization
|
|
header_value: Token 0123456789abcdef0123456789abcdef01234567
|
|
|
|
# (2) Permit the RegisterRecord objecttype (S-19a). Objecten refuses to store an object whose
|
|
# objecttype it has not been configured with ("ObjectType with url=… is not configured"), and it
|
|
# identifies one by uuid — which is why infra/objecttypen-registerrecord/register.py pins that uuid
|
|
# instead of letting Objecttypen assign one. Keep the two in step.
|
|
objecttypes_config_enable: true
|
|
objecttypes:
|
|
items:
|
|
- uuid: 1f4b4e26-8b1f-4e2f-9d6c-6a1b7a2f0e01
|
|
name: RegisterRecord
|
|
service_identifier: objecttypen
|
|
|
|
# (3) Static API token peers use to write/read objects.
|
|
tokenauth_config_enable: true
|
|
tokenauth:
|
|
items:
|
|
- identifier: register-referentie
|
|
token: 1234567890abcdef1234567890abcdef12345678
|
|
contact_person: Register Referentie
|
|
email: admin@localhost
|
|
organization: Respellion
|
|
is_superuser: true
|