Skip to content

Refactor VaultBackend to centralize secret path resolution and retrieval logic#62643

Open
SameerMesiah97 wants to merge 1 commit intoapache:mainfrom
SameerMesiah97:VaultBackend-Refactor
Open

Refactor VaultBackend to centralize secret path resolution and retrieval logic#62643
SameerMesiah97 wants to merge 1 commit intoapache:mainfrom
SameerMesiah97:VaultBackend-Refactor

Conversation

@SameerMesiah97
Copy link
Contributor

Description

Refactored VaultBackend to eliminate duplicated secret path resolution and secret retrieval logic across get_response, get_variable, and get_config. These methods previously repeated mount parsing, base path handling, path construction, and invocation of _VaultClient.get_secret.

This change introduces a private helper that centralizes path resolution and secret fetching, while preserving the existing post-processing behavior in each public method.

Rationale

The previous implementation duplicated non-trivial mount parsing, path construction, and secret retrieval logic in three separate methods. Centralizing this logic reduces maintenance risk and prevents divergence between connection, variable, and config resolution paths. This refactor improves internal structure without altering semantics.

Tests

No new tests were added. Existing tests already validate mount handling, path resolution, and secret retrieval behavior.

Backwards Compatibility

No changes to public APIs or behavior. This is an internal refactor only.

…ng logic

Introduce a private helper to remove duplicated mount parsing,
base path handling, and get_secret invocation across public methods.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant