Add a registry to support long lived instances during environment processing #22956
Assignees
Labels
theme: config-data
Issues related to the configuration theme
type: enhancement
A general enhancement
Milestone
Comments
|
The specific request is to support vault's session (/cc @mp911de) in spring cloud vault and a curator connection in spring cloud zookeeper. This may be applicable for other future config data implementations in GCP, Azure, AWS or Alibaba (which all have spring cloud |
philwebb
changed the title
philwebb
added a commit
that referenced
this issue
Aug 21, 2020
Add a simple `BootstrapRegistry` that can be used to store and share object instances across `EnvironmentPostProcessors`. The registry can be injected into the constructor of any `EnvironmentPostProcessor`. Registrations can also perform additional actions when the `ApplicationContext` has been prepared. For example, they could register the the bootstrap instances as beans so that they become available to the application. See gh-22956
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently
ConfigDataLocationResolverandConfigDataLoaderonly support ephemeral connections and object instances. For some technologies, these might be expensive to create. It would be helpful if we could provide some mechanism to manage the lifecycle of such instances. It would also be nice if they could sometimes get converted into true bean instances that can be registered in the application context.The text was updated successfully, but these errors were encountered: