sethvargo/vault-init

Issues

• It fails with ACCESS_TOKEN_SCOPE_INSUFFICIENT"

  #16 opened 3 years ago by laith-leo
  3

• Beware: docker tags 0.1.1 and 0.1.2 were overwritten with default behavior changed

  #10 opened 4 years ago by joemiller
  2

• TLS verification default changed to enabled by default, but no way to specify CA bundle

  #9 opened 4 years ago by joemiller
  0

• `/etc/ssl/certs/ca-certificates.crt: permission denied` will be fired.

  #7 opened 4 years ago by yagince
  1

• it stucks on "http: server gave HTTP response to HTTPS client"

  #13 opened 5 years ago by occelebi
  2

• Rotating Key Support

  #6 opened 5 years ago by somejavadev
  1

• Vault init with AWS KMS and Consul

  #5 opened 6 years ago by sandeepsharmadevops
  1