vaultenv

> Also, regarding DevOps, the tooling around Nix makes it a little brittle for anything event based--rapidly changing configurations on the fly due to network conditions (Consul, Ansible, etc). This is where configuration management is heading, and due to the static nature of Nix, delegating dynamic changes is hard/anti pattern. Channable uses Consul, Vault, etc. for dynamic configuration and it works with Nix just fine. You don't have to use static configuration files with Nix. Either fetch dynamic stuff using the Consul, Vault, etc. APIs at runtime or use a tool like vaultenv [1] or similar if you don't want this logic in your application code. Put those tools in your systemd service before launching your app, and you're good to go. (NB: I was DevOps teamlead at Channable while a part of this work was being done. Sad that I haven't seen

At Channable, we have had a great experience introducing Haskell for our infrastructure projects. We have written a few blog posts about this which you can find on our tech blog[1]. - Jobmachine, an advanced job-scheduling system with dynamic dependency resolution[2] - Vaultenv, a small open-source tool to get secrets from Hashicorp vault[3][4] - alfred-margaret, a blazingly-fast Aho-Corasick implementation written in Haskell[5][6] - Sharkmachine, our in-house replacement for Apache Spark[7] [1]: https://tech.channable.com/ [2]: https://tech.channable.com/posts/2017-02-24-how-we-secretly-... [3]: https://tech.channable.com/posts/2017-07-06-introducing-vaul... [4]: https://github.com/channable/vaultenv [5]: https://tech.channable.com/posts/2019-03-13-how-we-made-hask... [6]: https://github.com/channable/alfred-margaret [7]: https://tech.ch