The JSON index page does not contain the urn, so the current implementation has to retrieve all instruments to determine what the urn is. A partial download or adding the URN to the index overview would make this more efficient.
Also, the instruments downloaded are not cached, so always retrieved.
Also, the instrument service is always created when needed, this is not efficient (but this also hits the issue above).
Technical implementation
Make an FastAPI endpoint (on the instrument registry repository) of the instrument registry with production set-up
2 endpoints:
GET / (current index.json) -> redirect or serve from memory
GET /urn/<URN> (urn.json for a specific task/instrument)
Deploy on kubernetes on its own namespace
Linting, formatting, testing -> as we have this already in AMT
Sonar cloud
Next tickets
Implement a search functionality to search for text in specific urns
Description
The JSON index page does not contain the urn, so the current implementation has to retrieve all instruments to determine what the urn is. A partial download or adding the URN to the index overview would make this more efficient. Also, the instruments downloaded are not cached, so always retrieved. Also, the instrument service is always created when needed, this is not efficient (but this also hits the issue above).
Technical implementation
Make an FastAPI endpoint (on the instrument registry repository) of the instrument registry with production set-up
2 endpoints:
GET /
(current index.json) -> redirect or serve from memoryGET /urn/<URN>
(urn.json for a specific task/instrument)Deploy on kubernetes on its own namespace Linting, formatting, testing -> as we have this already in AMT Sonar cloud
Next tickets
Implement a search functionality to search for text in specific urns