-
Notifications
You must be signed in to change notification settings - Fork 146
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
What's the future of this plugin? #242
Comments
The plugin continues to function as vault has a stable API. I am hoping for something to create a fork of vault-java-driver and maintain it |
I believe there is now a fork/more maintained version of the vault-java-driver: reported/linked to from here: I know it's no easy undertaking, and the usual logic with things like this is that if anyone would like to see a change made, they are free to make that change and open a PR themselves, but I am curious if switching to this vault-java-driver is anywhere on the roadmap for this plugin. |
It might also be worth considering migrating away from vault-java-driver entirely... that project seems to have made some rather odd implementation choices concerning how it handles KV v1 vs v2 secret engines, which have leaked into this Jenkins plugin's API too in confusing ways:
which are also sometimes inconsistent:
There are multiple user reports in this issue tracker of difficulties working with KV v2 successfully, because of these challenges. I'm happy to provide further help designing any changes anyone sets out to make in this regard, though I don't currently see myself as likely to work on this directly, as I'm no longer in a role that involves working with any Vault-integrated Jenkins instances. |
Neither am I, only here to provide assistance on code review. I stopped using Jenkins a while ago 😓 |
BetterCloud/vault-java-driver contributor has announced that the project is effectively dead so what's the long term plan for this plugin?
The text was updated successfully, but these errors were encountered: