Skip to content

Conversation

@skyflow-vivek
Copy link
Collaborator

This PR adds support for adding custom vault URL directly through config parameters in V3 SDK.

  • Refactor VaultConfig POJO to V2 and V3 modules along with unit tests.
  • Made necessary changes to common module including cleaning imports.
  • Added vaultURL config parameter only for V3 module's VaultConfig.
  • Added unit tests and logic for proper prioritisation of vaultURL.
  • Added validations to ensure atlease one of vaultURL or clusterId is provided.

Why

  • There is a specific requirement for adding support for passing custom vault URL directly through config parameters in V3 SDK.

Goal

  • Users should be able to pass vaultURL both as ENV variable and/or as config parameter.
  • Prioritisation hierarchy is -> vaultURL (env) > vaultURL (config) > clusterId (config).

Testing

  • Added proper unit tests for the changes.
  • Manually tested multiple scenarios to ensure prioritisation is accurate.

skyflow-vivek and others added 5 commits November 26, 2025 15:40
- Refactor `VaultConfig` POJO to `V2` and `V3` modules along with unit tests.
- Made necessary changes to `common` module including cleaning imports.
- Added vaultURL config parameter only for `V3` module's `VaultConfig`.
- Added unit tests and logic for proper prioritisation of `vaultURL`.
- `vaultURL` (config) > `vaultURL` (env) > `clusterId` (config).
- Added validations to ensure atlease one of `vaultURL` or `clusterId` is provided.
- New priority order is: vaultURL (env) > vaultURL (config) > clusterId (config)
…ltURL-in-config-params

SK-2418 Add vaultURL as config parameter in VaultConfig
@skyflow-vivek skyflow-vivek merged commit 45442a5 into beta-release/25.11.2 Nov 27, 2025
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants