<p>In the hope of resurrecting this question, I will give my opinionated answer.</p>

<p>As I understand it, the use of Vault is part of the drive to give <strong>more autonomy to teams</strong>, by removing fear of leaking or changing secrets. By providing somewhere to store and manage secrets, ops can give dev the means to continue developing at their own pace, following the practices of continuous integration and working in small batches.</p>

<p>With a product like Vault in the pipeline, secrets can be consumed safely in the various phases - build, test, bake, deploy, etc. Implementing Vault in practice means less personal interaction with the service, but more machine interaction with the service, from trusted components in the pipeline.</p>

CC BY-SA 4.0
2019-12-10T10:53:24.240Z
2019-12-10T10:53:24.240Z
Bruce Becker
<p>I have read several Hashicorp Vault tutorials and one of the features that could be used is generating ssh keys for git clone repositories, but that implies that everybody in the company that clones repositories should install vault and an helper like <a href="https://github.com/hashicorp/vault-ssh-helper" rel="nofollow noreferrer">https://github.com/hashicorp/vault-ssh-helper</a></p>

CC BY-SA 4.0
2019-01-30T07:40:47.137Z
@simbo1905 I am curious what people encountered when they implemented Vault. Perhaps it is a very broad question and I should scope it more the more I think about it.
030
<culture><hashicorp-vault>
What does implementing Hashicorp Vault mean in practice?
030
# What does implementing Hashicorp Vault mean in practice?

(Asked by: username_0 on 2019-01-27)

I have read several Hashicorp Vault tutorials and one of the features that could be used is generating ssh keys for git clone repositories, but that implies that everybody in the company that clones repositories should install vault and an helper like <https://github.com/hashicorp/vault-ssh-helper>

**Tags:** culture, hashicorp-vault

> **Comments:**
> **username_0**: @simbo1905 I am curious what people encountered when they implemented Vault. Perhaps it is a very broad question and I should scope it more the more I think about it.  

---

## 1 answers

### Answer by username_1 on 2019-12-10. Score: 1 | Accepted answer

In the hope of resurrecting this question, I will give my opinionated answer.

As I understand it, the use of Vault is part of the drive to give **more autonomy to teams**, by removing fear of leaking or changing secrets. By providing somewhere to store and manage secrets, ops can give dev the means to continue developing at their own pace, following the practices of continuous integration and working in small batches.

With a product like Vault in the pipeline, secrets can be consumed safely in the various phases - build, test, bake, deploy, etc. Implementing Vault in practice means less personal interaction with the service, but more machine interaction with the service, from trusted components in the pipeline.


---

