Admin API part 3

[jbygdell]

Related issue(s) and PR(s)
None

Description
This PR mainly adds the ways to define which users should have admin access.

How to test

[aaperis]

Nice!

[nanjiangshu]

Great work!

Apart from the comments in the code, I have a few other comments:

1. When I tested with the following command

$ curl -s -w "%{http_code}\n" -H "Authorization: Bearer $token" -H "Content-Type: application/json" -X POST -d '{"accession_id": "my-id-01", "filepath": "/uploads/file.c4gh", "user": "testuser"}' http://localhost:8090/file/accession

It's a bit weird that the return code is 000.

2. I got an empty list for the following command

curl -H "Authorization: Bearer $token"  "http://localhost:8090/users/[email protected]/files" 

However, I got

$ curl -H "Authorization: Bearer $token"  "http://localhost:8090/files"
[{"inboxPath":"requester_demo.org/data/file1.c4gh","fileStatus":"uploaded","createAt":"2024-08-09T14:28:14.43718Z"}]

and

$ curl -H "Authorization: Bearer $token"  "http://localhost:8090/users"
["[email protected]","[email protected]"] 

What did I do wrong?

3. Formatting in the README: Error code for each API endpoint section should be under the section, for example

* /file/ingest
    - accepts POST requests with JSON data with the format: {"filepath": "</PATH/TO/FILE/IN/INBOX>", "user": "<USERNAME>"}
    - triggers the ingestion of the file.
* Error codes
    - 200 Query execute ok.
    - 400 Error due to bad payload i.e. wrong user + filepath combination.

should be changed to

- /file/ingest
    - accepts POST requests with JSON data with the format: {"filepath": "</PATH/TO/FILE/IN/INBOX>", "user": "<USERNAME>"}
    - triggers the ingestion of the file.

    * Error codes
        - 200 Query execute ok.
        - 400 Error due to bad payload i.e. wrong user + filepath combination.

[pontus]

Would admin.usersFile work instead of admin.configFile, while it is undoubtedly a configuration, configFile makes me think it could possibly controls more things.

[jbygdell]

Would admin.usersFile work instead of admin.configFile, while it is undoubtedly a configuration, configFile makes me think it could possibly controls more things.

Yes, that would improve readability.

[aaperis]

Minor suggestions :-)

[aaperis]

Looks good :-)