Currently there is a way to specify via mod-configuration how many access types could be created in mod-kb-ebsco-java.
Requirements: Use only static value for the config with env variables. Default value = 15 (already defined with kb.ebsco.credentials.access.types.limit)
We need it to not use mod-configuration as it deprecated
It’s exactly about transition (transition to mod-settings is not preferred; it’s better to do a transition to internal storing of the configurations)
The current default value is 15 if there is no value in mod-configuration. There is a question if it should be configurable in runtime ( with mod-settings or internal config) or if it could be a static value: 15, 25 or any.
Khalilah Gambrell March 10, 2025 at 2:53 PM
@Pavlo Smahin1. Why do we need to do this change? 2. Should we wait to do this change until we transition from mod-configuration to mod-settings? What if we set the limit to 25?
Currently there is a way to specify via mod-configuration how many access types could be created in mod-kb-ebsco-java.
Requirements:
Use only static value for the config with env variables. Default value = 15 (already defined with
kb.ebsco.credentials.access.types.limit)