Updates of the vault service no longer cut your connections
We can now update the service that holds your vault values without cutting git, API or database connections that run through it. Long answers through a vault entry no longer stop halfway.
If you use vault entries set to use only or locked, updates of the vault service no longer cut your git, API or database connections, and long answers no longer stop halfway. No action needed.
Your vault values in the states use only and locked live in a separate service. It adds the real value to a request from your workspace, so the workspace only ever sees a placeholder. Until now, every update of that service cut the git, API and database connections that were running through it at that moment.
Text version
The new version starts and is checked before it gets any traffic. Then new requests move to it in one step, and for one minute we can switch back at once. The old version takes no new requests, lets open connections finish and then stops. The new version knows the short-lived passes the old one handed out and writes to the same audit trail.
What changed
An update now starts the new version next to the old one. New requests go to the new version. The old one finishes the connections it already has and only then stops. A git push, a long download or an open database session keeps running while we update.
Long answers through a vault entry also no longer stop halfway when the target closes its side early. Before, a large git fetch through a slow connection could end with a TLS error.
What stays the same
Your values still never reach your workspace or our main server. Alerts about changes to your vault still reach you by push and mail, now through a different mail provider.
Do I need to do anything?
No.
Prices, plans and terms did not change.