just downloaded the hvac client yesterday and running into an issue. We run Vault in kubernetes with auto-unseal via aws kms. When I refactored our code for unsealing from running vault operator init -recovery-shares=1 -recovery-threshold=1 -> to using hvac with vault_client.sys.initialize(1, 1) it does not seem to work
continuously get this error: recovery configuration must specify a positive number of shares
vault is running in HA mode with 3 replicas
our storage backend for vault is postgres
Instead say
vault_client.sys.initialize(recovery_shares=1, recovery_threshold =1)
yeah i always go straight to source
if you saw it incorrectly ordered in the docs lmk and we can update
:) glad its working for you!
might have miss-understood this section but the initialize section seemed to imply they are the first 2 params in order
thanks for pointing that out!
yep, great client btw, i was parsing yaml until i found it =/
of the recent issues triaged this weekend 🤙
thats typically what i do when im traveling too, open source work
@jeffwecan apparently i can commit directly to
develop hvac/hvac@b2940d6 . i thought my git config was set to default to my fork but apparently not
I suppose we can bypass the branch protection since the "Include Administrators" option isn't checked
looks like you could maybe just back those commits out though?:
git checkout develop
git reset --hard 43ce194603d7bff84d4f219b93210778800aac89
git push --force [...]
did you enable protection?
I suppose a force push hits some other setting?
ty
sorry about that...
D:
probably should read up more on github's branch protection settings since I'm clearly missing something :shrug:
*adds to long list of todos
since you force pushed to an extant commit, I think your commits are still properly based on develop proper
ill open a pr against dev and see if it barfs