vault: Kv1 hardcoded path prevents use of Kv2 secrets

[ellipsis-me]

Plugin Name

@backstage-community/plugin-vault

📜 Description

Here I see a problem trying to use Kv2 secrets, the v1/secrets/ path does not allow the use of Kv2 secrets as the Official Docs mention here, the snippet above must be changed in case the use of Kv2 secrets to accomplish the right path /:secret-mount-path/data/:path?version=:version-number, As we can see, to use Kv2, this v1/secrets/ must become this :secret-mount-path/data/. In my tests, I got that happening /api/vault/v1/secrets/***-secret?engine=***, the engine is being used as query params which the Vault API does not allow.

👍 Expected behavior

The correct validation of the plugin while using Kv2 secrets, as the documentation shows.

👎 Actual Behavior with Screenshots

In my tests, I got that happening /api/vault/v1/secrets/***-secret?engine=***, the engine is being used as query params which the Vault API does not allow for Kv2 secrets, or Kv1 in other mountpaths besides the default secrets hardcoded.

👟 Reproduction steps

Try to use Kv2 secrets, or Kv1 in other mountpaths besides the default secrets.

📃 Provide the context for the Bug.

No response

👀 Have you spent some time to check if this bug has been raised before?

• I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

• I have read the Code of Conduct

Are you willing to submit PR?

Yes I am willing to submit a PR!

[vinzscam]

@ellipsis-me would you like to be assigned?

[ellipsis-me]

@vinzscam Ok, I'll make some changes and request for your review.

[AdrianKrajewski001]

@ellipsis-me We encountered the same problem. Maybe I can help you in some way?