[FOLIO-1872] Several modules have a submodule configuration that refer to a non-existent branch of mod-users Created: 14/Mar/19  Updated: 03/Jun/20  Resolved: 15/Mar/19

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

Type: Bug Priority: P2
Reporter: John Malconian Assignee: Adam Dickmeiss
Resolution: Done Votes: 0
Labels: platform-backlog
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Relates
relates to MODINVSTOR-272 PR test failure / timeout / constrain... Closed
Sprint:
Development Team: Core: Platform

 Description   

mod-inventory-storage, mod-login, mod-permissions, and possibly other modules have a submodule configuration that points to a non-existent branch of mod-users that was deleted (modusers-103-load-reference). This is/will cause builds in Jenkins to fail. I've temporarily restored the missing branch in Github, however, the submodule configuration for each of these modules needs to be updated to presumably point to the master branch of mod-users.



 Comments   
Comment by Adam Dickmeiss [ 15/Mar/19 ]

So sorry.. Because the modusers-103 branch was squashed the pointer became invalid.

Comment by Marc Johnson [ 15/Mar/19 ]

Out of curiosity, why do these modules have a submodule for mod-users? Are we using it to define the users referenced in the sample records?

Comment by Adam Dickmeiss [ 15/Mar/19 ]

Yes. 300 sample user records. And the userId's have to match up.

Comment by Marc Johnson [ 15/Mar/19 ]

Does that mean that some of the sample records for mod-inventory-storage are generated based upon the user records in the submodule?

Comment by Adam Dickmeiss [ 15/Mar/19 ]

Yes

Comment by Adam Dickmeiss [ 15/Mar/19 ]

The 3 modules have updated their mod-users pointer

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