Extend IBM DevOps deploy Vault integration to support multiple vault environments(Specifically Open Source)

  IBM DevOps Deploy (UCD )is currently able to integrate with enterprise harshicorp vault instance for secret retrieval during deployment. This integration is functional and in active use for the pipelines.

  However, our Organization operates on a Open source vault environment called OSV Vault, which hosts secrets for a different set of applications and deployment pipelines, Currently IBM DevOps Deploy does not support seamless configuration to point OSV Vault instance -Creating gap in our secret management strategy.

  We propose that IBM DevOps Deploy natively supports the ability to configure and connect the multiple Harshicorp vault instance (Specifically OSV instance) within the UCD - allowing different applications or environments to pull secrets their designated vault instance (HSV,OSV) independently without confilct.

  Current limitation:

• UCD's Existing vault configuration appears to support a single endpoints vault (enterprise ).
• When attempting to configure OSV as an additional vault source using approle authentication, We encountered HTTP 403 error that are not reproducible when testing the same credentials directly Via postman.
• There is no clear documentation covering OSV instance configuration within a UCD store.
• This forces teams managing OSV-connected applications to use workarounds (Manual scripts) instead of the native UCD vault integration.

  Expected Outcomes:

• Multi environment support- Enable teams using different vault instance (HSV,OSV) to use natively without workarounds.
• Reduced risk - Eliminates the need for custom scripts to bridge the gap, reducing pipeline maintenance overhead.
• UCD application or components should be able to refer a specific vault instance.
• Consistency - All secrets retrieval follows the same governed, auditable path regardless of which vault instance is targeted.