Description
Hello there, I was looking into improving the support of OpenBao.
It works fine with the current hashivault provider, but it relies on the VAULT_ADDR/VAULT_TOKEN environment variables.
For our users, we'd like for them to be able to use cosign with the BAO_ADDR/BAO_TOKEN environment variables to avoid confusion.
Ideally we would also like to see a dedicated provider with its own scheme (e.g openbao://).
I'm happy to submit a PR. But wonder if it's best to just duplicate the hashivault provider or if you'd like this to be implemented differently?
Description
Hello there, I was looking into improving the support of OpenBao.
It works fine with the current
hashivaultprovider, but it relies on theVAULT_ADDR/VAULT_TOKENenvironment variables.For our users, we'd like for them to be able to use cosign with the
BAO_ADDR/BAO_TOKENenvironment variables to avoid confusion.Ideally we would also like to see a dedicated provider with its own scheme (e.g
openbao://).I'm happy to submit a PR. But wonder if it's best to just duplicate the
hashivaultprovider or if you'd like this to be implemented differently?