/
Removing mod-configuration after Sunflower release
Removing mod-configuration after Sunflower release
Goal of this subgroup is to ensure mod-configuration can be removed after Sunflower release according to https://github.com/folio-org/rfcs/blob/master/text/0006-folio-distributed-vs-centralized-configration.md.
To achieve this, the following has to be done:
check for dependencies of modules on mod-configuration
check, if frontend queries mod-configuration
communicate to developer groups about the RFC
create Jira issues for modules that still use mod-configuration
talk to maintainers of mod-configuration about the removal of write operations during the sunflower release.
Members: @Florian Gleixner @Jeremy Huff
, multiple selections available,
Related content
Migration from mod-configuration and mod-settings
Migration from mod-configuration and mod-settings
More like this
Sunflower
Sunflower
More like this
Deprecation Policy for FOLIO Modules outside of the official supported set with a Severe Security Vulnerability
Deprecation Policy for FOLIO Modules outside of the official supported set with a Severe Security Vulnerability
More like this
DR-000034 - Java 17 Support
DR-000034 - Java 17 Support
More like this
Changes and required actions
Changes and required actions
More like this
DR-000039 - Distributed vs. centralized configuration
DR-000039 - Distributed vs. centralized configuration
More like this