If many different "states" are used for one big architecture, how are the boundaries between them managed?
Under one state, Terraform will spot issues here during `plan`, but with many states issues will only appear after `apply`.
Under one state, Terraform will spot issues here during `plan`, but with many states issues will only appear after `apply`.
Ahh why?! Scala is FP larping as OOP. Great type system, poor syntax.
Why would you need to deal with anonymity?
Presently I use Bitwarden (with a selfhosted Vaultwarden backend) for this reason, and block the phone-home spyware the Bitwarden people ship in the client with DNS blackholing.
Happy to replace it if: a) there is an import path from Bitwarden and b) a good client for iOS that supports the native iOS password manager APIs. I expect further enshittification from Bitwarden in the future, and keep a close eye on new projects like this one as a result.
Managing a vault server sounds like a pain.