Skip to content

docs: correct four known errors (group-status catalog, /dbfields writes, group-type change, provider link) - #188

Merged
2000game merged 2 commits into
mainfrom
docs/correct-known-errors
Sep 26, 2026
Merged

2000game merged 2 commits into
mainfrom
docs/correct-known-errors

Conversation

@2000game

Copy link
Copy Markdown
Member

Found while cataloguing everything we know about ChurchTools (eqrm/ct-structure docs/wissenskatalog/, 2026-09-26). Docs only, no code changes.

Claim in the docs Actually Evidence
Group statuses have no REST catalog (#67) GET /person/masterdata → groupStatuses: 1 active, 2 pending, 3 archived, 4 finished #157; read live on prod and dev 2026-09-26, identical
/dbfields is GET-only The prod OpenAPI spec lists POST /dbfields, PUT/DELETE /dbfields/{id} and CRUD on /options /system/runtime/swagger/openapi.json, 2026-09-26. Not live-tested, so the tool behaviour is unchanged
groupTypeId is a normal managed field Changing it needs POST /groups/{id}/grouptype + role mapping; a normal update returns 400 #171
Provider repo "not public yet" Public, v0.3.0 eqrm/terraform-provider-churchtools

The #182 doc fixes (group_type_role is role-keyed) are in #187, not here.

Checks: prettier --check passes. Some table rows were only re-aligned by prettier.

…es, group-type change, provider link)

- Group statuses DO have a read catalog: GET /person/masterdata -> groupStatuses
  (1 active, 2 pending, 3 archived, 4 finished; identical on eqrm prod and dev). #67 missed
  it; ct still does not resolve by name (#157).
- /dbfields: the prod OpenAPI spec now lists POST/PUT/DELETE, including options. Not
  live-tested; ct keeps treating field definitions as read-only.
- groupTypeId cannot change through the regular group update. It needs
  POST /groups/{id}/grouptype with a role mapping (#171).
- README: the provider repo is public and released.
@2000game
2000game merged commit 4e09510 into main Sep 26, 2026
3 checks passed
@2000game
2000game deleted the docs/correct-known-errors branch September 26, 2026 12:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant