Skip to content
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

Add custom Vault Authentication Path when using k8s login method #27

Merged
merged 2 commits into from
Apr 6, 2023

Conversation

dttung2905
Copy link

@dttung2905 dttung2905 commented Mar 29, 2023

Hi @jopenlibs,

Thanks for maintaining this fork so actively. You are doing a great work for the community 🙏

This PR aims to solve the hardcoding authentication path for Vault. This is extracted from the official doc

The default endpoint is auth/kubernetes/login. If this auth method was enabled at a different path, use that value instead of kubernetes

This is related to another issue lensesio/secret-provider#46 that I'm trying to fix ( and hopefully pin the vaul-java-driver dependencies to your fork 🤞 )

Do let me know if you have any comments/ feedback on this.

@dttung2905
Copy link
Author

Hi @henryx,
Could you help to take a look at this PR if you have time please 🙏 ?

@henryx
Copy link
Collaborator

henryx commented Apr 6, 2023

Hi @dttung2905, thank you for you PR, I've viewed it and for me is good. After the merge, I release ASAP the new version, to accomplish your work. In future, feel free to write tests for this part (sadly, I have no idea how to mock them)

@henryx henryx merged commit 2e8cf71 into jopenlibs:master Apr 6, 2023
@dttung2905
Copy link
Author

Hi @henryx,
Thanks for the quick reply and the approval. May I know the latest new version would be 5.3.0 according to this page right?

@henryx
Copy link
Collaborator

henryx commented Apr 12, 2023

@dttung2905 yes I've released the latest version. Sadly, for now, I cannot uploaded to Maven Central, so you need to build it manually

@dttung2905
Copy link
Author

@henryx thanks for the help to release. Is there any timeline that we can solve the maven central problem?

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.

2 participants