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.

Sign up for GitHub

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

Jump to bottom

Extend safe so it can initialize and unseal vault in HA or non-ha mode. #34

Closed
norman-abramovitz opened this issue Jul 12, 2016 · 3 comments
Closed

Extend safe so it can initialize and unseal vault in HA or non-ha mode. #34

norman-abramovitz opened this issue Jul 12, 2016 · 3 comments
Assignees
@dennisjbell

Comments

@norman-abramovitz
Copy link
Contributor

Extend safe to initialize and unseal vault. Should deal with ha standby copies as well.
@jhunt
Copy link
Contributor

jhunt commented Jul 29, 2016

This is mostly working for DNS (PR forthcoming), but we need to modify it to handle old-school Vault deployments as well as 0.6.0+ deployments. This necessitates moving from DNS-based resolution to straight TCP/HTTP Consul API, a non-trivial undertaking.

@jhunt jhunt mentioned this issue Aug 16, 2016
Merged
@jhunt
Copy link
Contributor

jhunt commented Nov 7, 2016

Just put in #58, as an alternative solution to this problem that plays well, but requires a new BOSH release.

@jhunt
Copy link
Contributor

jhunt commented Nov 11, 2016

#58 is merged. This will work if you are using strongbox with the safe-boshrelease

@jhunt jhunt closed this as completed Nov 11, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dennisjbell dennisjbell

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@jhunt @dennisjbell @norman-abramovitz