decouple the secrets helper from connectors, to support secrets in ot… #17771
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.
What
Support secrets in other config types apart from just connectors.
This will let us re-use the existing secrets management logic for secrets that live in other places -- e.g., a webhook operation config table.
There are other possible refactors here, but this is a minimal change to enable code reuse to support webhook operations.
How
Replace the
ConnectorSpecification
in the SecretsHelper API with the underlying JsonNode.We eventually always pull the JsonNode out, so this just pushes it one layer higher to make the SecretsHelper more generic.
Recommended reading order
airbyte-config/config-persistence/src/main/java/io/airbyte/config/persistence/split_secrets/SecretsHelpers.java