`POST /collections` could return the effective collection configuration #221

New issue

Open

opened 2026-06-24 06:51:30 +00:00 by mih · 1 comment

mih commented

2026-06-24 06:51:30 +00:00

Owner

This status quo is that nothing is returned:

❯ curl -X 'POST' \
  'http://localhost:8000/collections' \
  -H 'accept: application/json' \
  -H 'X-DumpThings-Token: some' \
  -H 'Content-Type: application/json' \
  -d '{
  "default_token": "token1",
  "curated": "curated1",
  "schema": "testschema.yaml",
  "incoming": "inbox1",
  "backend": {
    "type": "record_dir+stl",
    "mapping_method": "digest-md5"
  },
  "auth_sources": [
    {
      "type": "config"
    }
  ],
  "name": "collection1"
}'
null%

I wonder whether there is a reason behind that, or whether it would make sense and be better if the creation of a collection returns the full effective configuration for that collection. In other words, it would return what a subsequent GET on /collections/collection1 would return?

This status quo is that nothing is returned: ``` ❯ curl -X 'POST' \ 'http://localhost:8000/collections' \ -H 'accept: application/json' \ -H 'X-DumpThings-Token: some' \ -H 'Content-Type: application/json' \ -d '{ "default_token": "token1", "curated": "curated1", "schema": "testschema.yaml", "incoming": "inbox1", "backend": { "type": "record_dir+stl", "mapping_method": "digest-md5" }, "auth_sources": [ { "type": "config" } ], "name": "collection1" }' null% ``` I wonder whether there is a reason behind that, or whether it would make sense and be better if the creation of a collection returns the full effective configuration for that collection. In other words, it would return what a subsequent `GET` on `/collections/collection1` would return?

mih commented

2026-06-25 06:05:37 +00:00

Author

Owner

Still the case with v6.2