Done
Details
Assignee
Mukhiddin YusupovMukhiddin YusupovReporter
Khalilah GambrellKhalilah GambrellPriority
P3Story Points
3Sprint
NoneDevelopment Team
SpitfireFix versions
Release
Ramsons (R2 2024)TestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Assignee
Mukhiddin Yusupov
Mukhiddin YusupovReporter
Khalilah Gambrell
Khalilah GambrellPriority
Story Points
3
Sprint
None
Development Team
Spitfire
Fix versions
Release
Ramsons (R2 2024)
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created August 27, 2024 at 9:43 PM
Updated October 30, 2024 at 12:57 PM
Resolved September 23, 2024 at 4:03 PM
Requirement: Include Fetch MARC bib and MARC authority rules validation when setting up/upgrading an environment so that
Using reference environments (i.e. snapshot) does not require anyone to make the GET call to fetch these rules
Ramsons release and future release does not require hosting providers to do this fetch manually when installing this module
Validation
Whenever snapshot is rebuilt and/or any reference environment, will always have the MARC bib and MARC authority validation rules applied (verify on Okapi and Eureka environments)
Rancher environments will always have the MARC bib and MARC authority validation rules applied (verify on Okapi and Eureka environments)
Ensure that this requirement is a part of the module and is only automatically triggered when the module is implemented for first time. Do not automatically re-fetch new rules if the tenant has already had the module installed. We do not want a situation where an release upgrade causes an auto-fetch that results in a tenant recreating their validation rules.
Add release notes/documentation
Approach
Use
tenantExists
check ofTenantService
to execute specificationsync
logic on enabling tenant if tenant didn’t exist beforeF.e. override
createOrUpdateTenant
, calltenantExists
→super.createOrUpdateTenant
-> specificationsync