v6 test setup #222

New issue

Open

opened 2026-06-24 06:58:06 +00:00 by mih · 0 comments

mih commented

2026-06-24 06:58:06 +00:00

Owner

This is not an issue, but serves as a reference for other issues that report on the specific behavior of a v6 deployment set up using the steps shown below

Start the service in a directory that is empty, except for a testschema.yaml file with a LinkML schema to be used for a test collection.

dump-things-service --admin-token-hash a6b46dd0d1ae5e86cbc8f37e75ceeb6760230c1ca4ffbcb0c97b96dd7d9c464b --ignore-default-config-file .

The token hash is for the plain-text token "some".

Create the test collection:

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"
}'

Actually create the token token1 that has been anticipated in the collection setup above, as a curator token.

curl -X 'POST' \
  'http://localhost:8000/tokens' \
  -H 'accept: application/json' \
  -H 'X-DumpThings-Token: some' \
  -H 'Content-Type: application/json' \
  -d '{
  "user_id": "user1",
  "collections": {
    "collection1": {
      "mode": "CURATOR",
      "incoming_label": "user1inbox"
    }
  },
  "hashed": false,
  "representation": "mytoken",
  "name": "token1"
}'

This is not an issue, but serves as a reference for other issues that report on the specific behavior of a v6 deployment set up using the steps shown below Start the service in a directory that is empty, except for a `testschema.yaml` file with a LinkML schema to be used for a test collection. ``` dump-things-service --admin-token-hash a6b46dd0d1ae5e86cbc8f37e75ceeb6760230c1ca4ffbcb0c97b96dd7d9c464b --ignore-default-config-file . ``` The token hash is for the plain-text token "some". Create the test collection: ``` 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" }' ``` Actually create the token `token1` that has been anticipated in the collection setup above, as a curator token. ``` curl -X 'POST' \ 'http://localhost:8000/tokens' \ -H 'accept: application/json' \ -H 'X-DumpThings-Token: some' \ -H 'Content-Type: application/json' \ -d '{ "user_id": "user1", "collections": { "collection1": { "mode": "CURATOR", "incoming_label": "user1inbox" } }, "hashed": false, "representation": "mytoken", "name": "token1" }' ```

mih referenced this issue

2026-06-24 07:01:56 +00:00

ValueError: Cannot store Thing #223

mih referenced this issue

2026-06-24 12:26:03 +00:00

Resolve broken value encoding for HexBinary #226