werf
Secrets access levels
Access control when users work with secrets. For example, according to a specific company security policy, developers should not have access to production secrets.
Шифровать разными ключами? Подсунул ключ, доступно для редактирования только то, что расшифровалось. Подсунул другой, правишь продовые секреты.
There should be a way to store multiple layers of secrets in the single repo. Werf should have a way to give access to some secrets for some users only.
Maybe we can add support for 3rd-party secret management engines? For example, ansible-vault with vault ids as a simple solution or/and Mozilla SOPS?
The priority now is to stabilize version 1.2 and complete the remaining features, as well as to switch to the new update manager instead of multiwerf. After that, we will start with version 1.3.
I think November/December is the real ETA.
The priority now is to stabilize version 1.2 and complete the remaining features, as well as to switch to the new update manager instead of multiwerf. After that, we will start with version 1.3.
I think November/December is the real ETA.
Any updates on integration with SOPS?
We will most likely add it in version 1.2, but not as a priority. Now we focus on the documentation and the site. After that, we will reflect on the priority of this task in our Roadmap.
It feels like the Q1/Q2 of next year.
We are planning to migrate to SOPS in the next major release at the end of the year (3.0).