4.x: Introduces OciSecretsMpMetaConfigProvider, which adapts OciSecretsConfigSourceProvider to the MpMetaConfigProvider contract #7520
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR guesses somewhat blindly at how to adapt the existing
OciSecretsConfigSourceProvider
to theMpMetaConfigProvider
contract, prioritizing maximum code and meta-configuration reuse. I don't know if it is the correct recipe or not; this is just a guess (that works). Depending on how wrong I guess, I will either close this PR once I get the proper recipe and open a new one, or amend this PR to fix any flaws.Documentation impact: none yet
Update: following guidance, the recipe now:
MpMetaConfigProvider
(namedOciSecretsMpMetaConfigProvider
) that:OciSecretsConfigSourceProvider
thatConfigSource
Config
consisting of the HelidonConfigSource
so created andMpConfigSources#create(Config)
to create aList
of MicroProfile ConfigConfigSource
s from the resulting HelidonConfig