mistweaverco
@mistweaverco.com
We love ❤️ to make the world 🌎 a better place by giving you all the tools 📦 you need, but always for free 🤞 and driven by the community 🌈.
Kuba cache was an opt-in (default off) necessity for us, before adding 1password and bitwarden support, because they have a ridiculously strict rate-limit, which makes it nearly impossible to use without caching.
October 5, 2025 at 4:19 PM
Kuba cache was an opt-in (default off) necessity for us, before adding 1password and bitwarden support, because they have a ridiculously strict rate-limit, which makes it nearly impossible to use without caching.
- opt-in caching of secrets (see `kuba config cache -h`)
- cached secret management (see `kuba cache -h`)
- easier update via `kuba update`
- string interpolation has been fixed (e.g. `value: "${DB_IP}:${DB_PORT}`)
- cached secret management (see `kuba cache -h`)
- easier update via `kuba update`
- string interpolation has been fixed (e.g. `value: "${DB_IP}:${DB_PORT}`)
October 5, 2025 at 4:19 PM
- opt-in caching of secrets (see `kuba config cache -h`)
- cached secret management (see `kuba cache -h`)
- easier update via `kuba update`
- string interpolation has been fixed (e.g. `value: "${DB_IP}:${DB_PORT}`)
- cached secret management (see `kuba cache -h`)
- easier update via `kuba update`
- string interpolation has been fixed (e.g. `value: "${DB_IP}:${DB_PORT}`)