[FOLIO-3732] Add mod-consortia module to snapshot reference environment and vagrant snapshot VM Created: 03/Mar/23  Updated: 16/Mar/23  Resolved: 16/Mar/23

Status: Closed
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: Task Priority: TBD
Reporter: Serhii_Nosko Assignee: David Crossley
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Blocks
is blocked by FOLIO-3733 mod-consortia Dockerfile: apt upgrade Closed
Cloners
clones FOLIO-3159 Add edge-caiasoft module to testing e... Closed
Sprint: DevOps Sprint 160
Development Team: FOLIO DevOps

 Description   

Overview:

A new back-end module https://github.com/folio-org/mod-consortia should be added to the folio-snapshot reference environments as well as for the Vagrant VM boxes for folio-snapshot etc for testing and demo purposes.

Acceptance Criteria:

  • mod-consortia module have been added to folio-snapshot etc. and to appropriate vagrant boxes


 Comments   
Comment by Jakub Skoczen [ 06/Mar/23 ]

To be verfied before we add this.

Comment by David Crossley [ 09/Mar/23 ]

One thing that needs to be verified, is that the responsible team (which is not in matrix) is absolutely sure about the name.

Our DevOps team does not have the resources to go through the rename procedure.

The repository README gives no clues about its purpose, and this Slack thread indicates that its purpose is not yet established.

consortium:
Is an association and partnership of several entities participating in a common activity.

consortia:
Is the plural form – a number of consortiums.

Comment by Serhii_Nosko [ 09/Mar/23 ]

Hi David Crossley, I think Thunderjet will be responsible for this module, we will update matrix soon.

Also we are going to update Readme soon as well.

Regarding module name  - it was agreed with architects and this name mod-consortia was used in all architecture diagrams.

Comment by David Crossley [ 10/Mar/23 ]

The initial ModuleDescriptor has endpoint "pathPattern": "/consortia/tenants" ("Get a list of tenants").

And the associated API schemas (tenantCollection.json and tenant.json) do not declare which particular consortium in which the tenant is participating. Nor does it handle the case where a tenant with the same name is participating in multiple consortiums.

So it seems that this module is handling a single consortium, and not a group of consortiums (i.e. consortia).

This ticket is in Blocked state until this is clarified beyond diagrams.

Comment by Olamide Kolawole [ 10/Mar/23 ]

David Crossley Confirming that we want to go with "mod-consortia". The API is still under development & we want a get working module in snapshot to allow development & testing iterations.

Comment by David Crossley [ 14/Mar/23 ]

Since the front-end module was already added to platform-complete snapshot branch before waiting for the back-end module, then now the back-end module can be added simply by the front-end module declaring the interface via its package.json file "okapiInterfaces" section.

As usual, with any major change be sure to watch the subsequent hourly platform build.

Comment by David Crossley [ 16/Mar/23 ]

No activity.

So i have added the back-end module separately to platform-complete snapshot branch pull/2351 and the subsequent hourly platform build was successful.

Missed today's folio-snapshot build, so it will be included in the later folio-snapshot-2 build.

It is now included in today's snapshot VM.

Generated at Thu Feb 08 23:30:17 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.