Y24-183 - Move Sequencescape API v1 calls over to API v2

[sdjmchattie]

User story

Sequencescape API v1 will be shut down in the near future and has been deprecated for the past 5 years. We should switch usage of the API over to v2, using the already installed json_api_client gem.

Who are the primary contacts for this story

Stuart McHattie

Who is the nominated tester for UAT

PSD

Acceptance criteria

To be considered successful the solution must allow:

• No more API v1 calls are made to Sequencescape
• All traces of sequencescape-client-api and its config have been removed.

Dependencies
Any new endpoints required in Sequencescape will have to be created as they are discovered to be missing. A new story should be created under that repository if there are indeed endpoints to create.

Additional context

The calls made during the last two week period are as below, with counts for each endpoint:

• GET - /api/1/: 17

• GET - /api/1/plate_purposes: 32

• GET - /api/1/plate_purposes/2: 16

• GET - /api/1/plate_purposes/3: 16

• GET - /api/1/plate_purposes/4: 16

• GET - /api/1/{uuid}: 17

• GET - /api/1/{uuid}/wells: 17

• POST - /api/1/{uuid}/extraction_attributes: 17

• POST - /api/1/{uuid}/plates: 16

[sdjmchattie]

Briefly reviewing the code and the list of calls being made to v1, I think we need to start using the PlatePurpose JSON API endpoint that was only created recently. This endpoint might need to be updated to support creating plates and extraction attributes as these are currently not obviously available in SequenceScape. I don't think there are any actual new endpoints to create.