[FOLIO-3960] Hourly snapshot build fails because of the duplicate Okapi interfaces Created: 22/Jan/24  Updated: 22/Jan/24  Resolved: 22/Jan/24

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

Type: Bug Priority: TBD
Reporter: John Malconian Assignee: John Malconian
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Sprint:
Development Team: FOLIO DevOps
RCA Group: TBD

 Description   

mod-login and mod-login-keycloak both provide the same login interface and both module descriptors have been published to the project's okapi interface registry at https://folio-registry.dev.folio.org. Any build that uses this registry to resolve dependencies will fail with an error similar to the following:

interface login required by module folio_users-10.1.1000004763 is provided by multiple products: mod-login-keycloak, mod-login


 Comments   
Comment by John Malconian [ 22/Jan/24 ]

Craig suggested that one possible solution is to use Okapi 'filter' and 'provide' parameters to only include the interface provided by mod-login:

https://folio-registry.dev.folio.org/_/proxy/modules?provide=login&filter=mod-login

This solution works, however, due to the broader impacts to the FOLIO community who use folio-registry, the cleanest solution would be to remove the mod-keycloak-login module descriptor from the registry all together and to reconfigure the module's CI pipeline to not publish the module descriptor to folio-registry.

https://github.com/folio-org/mod-login-keycloak/blob/783da67aa0c12df906bc57c64be0e4667337f424/Jenkinsfile#L2

The module's MD can be posted directly to Okapi instances that require it for now. We can swap out mod-login for mod-login-keycloak on folio-registry at the appropriate time TBD.

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