-
Notifications
You must be signed in to change notification settings - Fork 1
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
Issue 1: update as many references as possible from vault to openbao #2
Conversation
Signed-off-by: jessebot <[email protected]>
Signed-off-by: jessebot <[email protected]>
Signed-off-by: JesseBot <[email protected]>
points at v1.9.3-0.20240330013750-f20d4684d48c instead and then I ran go mod tidy Signed-off-by: jessebot <[email protected]>
…drop support for testing unsupported versions of k8s Signed-off-by: jessebot <[email protected]>
Signed-off-by: jessebot <[email protected]>
Signed-off-by: JesseBot <[email protected]>
Signed-off-by: jessebot <[email protected]>
Signed-off-by: jessebot <[email protected]>
… has not changed upstream Signed-off-by: jessebot <[email protected]>
…ao-helm Signed-off-by: jessebot <[email protected]>
This is now ready for review and merge. The only portion that can't fully test is the integration with the helm chart, as it requires an image be pushed up, and we don't have that yet, but the rest of everything related to linting and testing passed, and you can verify it here: https://github.com/jessebot/openbao-csi-provider/actions/runs/9188218819 |
It seems like there are still some references in |
Description
bao
where appropriate)github.com/openbao/openbao/api
module to point at latest commit in upstream openbao/openbao repo and ran go mod tidy