Versioning strategy for HCP Vault Secrets API

HashiCorp Cloud Platform (HCP) HCP Vault Secrets
1

What is the summary of the versioning strategy for HCP Vault Secrets API?

In the api docs (HCP Vault Secrets | HashiCorp Developer), we see the 2023-06-13 (latest) and a 2023-11-28 (preview) dropdown values.

And these date values show up in the URL of the api (where v1/v2 used to happen)

Is versioning date based now? With ‘preview’ alluding to upcoming changes and ‘latest’ alluding to the stable latest version?

Appreciate any explanation and if api-docs can feature a section on versioning strategy

2

HCP Vault Secrets follows the versioning strategy as aligned with HCP. Docs for HCP are here - HCP API Overview | HashiCorp Cloud Platform | HashiCorp Developer

Versions are specific per service owning resources. Version names format is YYYY-MM-DD, for example, 2021-04-30.

Vault continues to have v1/v2 based versioning scheme.

3

thank you @kartik.lunkad . This is helpful