...
In Sunflower EBSCO will shift support from Okapi to Eureka.
In order for the community to transition to Eureka in Sunflower as well, these high level requirements/milestones should be met:
Hosting FOLIO community devops and hosting providers beyond EBSCO and FOLIO community devops are confident in operating Eureka
Developer documentation for working in the Eureka platform
Define flower releases using Eureka based applications
Replaces the release branches (e.g. 2024 R2) of current platform-complete definitions
May use a different repository
May want to be consistent with how the Eureka based Rancher environments are being defined
Build hosted reference environments using Eureka
Define environment configurations using Eureka based applications
Similar to above for flower releases, instead for the snapshot branch
Use Eureka based architecture
Including Keycloak, Kong, sidecars for module docker containers etc
Use Eureka management API to enable applications defined above
If the community is unable to shift to Eureka and must continue supporting the Okapi architecture these high level requirements will need to be met:
Community support for an Okapi-based bugfest environment
Community support for Okapi-based CSPs
Community dev ops is able to prove the Ramsons release of Okapi will run Sunflower modules and perhaps modules from future releases as well
How long does the community support Okapi? Does the community shift from Okapi to Eureka in Sunflower? Will the councils affirm an intention to shift to Eureka in Sunflower?
...