wildfly-security/wildfly-elytron-hashicorp-vault

Consider KV version utilities and enum in main code

Open

#81 opened on Jun 19, 2026

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Java (7 forks)auto 404
good first issue

Repository metrics

Stars
 (0 stars)
PR merge metrics
 (PR metrics pending)

Description

The KvVersionTestHelper class in test code contains a KvVersion enum and utilities that handle differences between KV v1 and v2:

KvVersion enum (V1/V2 with version numbers) Path construction for different versions (constructApiPath) Path validation (isValidPathForVersion) Secret name extraction (extractSecretName) Currently the main code handles KV version differences using string comparisons and inline logic. Having a proper enum and centralized utilities in production code would improve type safety and maintainability.

Considerations:

Separate test-specific methods (CLI, containers) from general utilities Main code would benefit from enum-based version handling Requires design discussion on production utility patterns Related: PR #71 review feedback

Contributor guide

Research direction
Examine current version handling in main code, review PR #71 feedback, and design a centralized enum and utilities for KV version differences following production patterns.
Tech stack
java
Domain
backend
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
JavaGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60