Skip to content

Added property resolver

Dmitrii Novikov (EPAM) requested to merge partition-property-resolver into master

Type of change

  • Bug Fix
  • Feature

Does this introduce a change in the core logic?

  • [YES]

Does this introduce a change in the cloud provider implementation, if so which cloud?

  • AWS
  • Azure
  • Google Cloud
  • IBM

Does this introduce a breaking change?

  • [NO]

What is the new/expected behavior?

  • The main goal is to move the commonly used property loading mechanism to the common library. This mechanism is widely used in GCP implementations and most likely will be useful for all CSPs.
  • In the past, these changes were used in mappers (OSM, OQM, OBM) and some OSDU services to load config properties.
  • Config properties are usually stored in Partition service as PartitionInfo, Secret service in the future, and, in case of secrets, config property can store a reference to ENV variable (when value loading not from Partition service directly, but from ENV variables for more security).
  • Proposed implementation in MR defines interface and Partition service-related implementation, which provides cache and sensitive/non-sensitive, mandatory/optional properties type.
  • Verbose and descriptive logging are also available.
  • Feature is enabled by propertyResolver.strategy=partition property, and no additional beans are added in the spring context if this property is not set
Edited by Dmitrii Novikov (EPAM)

Merge request reports

Loading