Git through vault entries no longer breaks off halfway
Git and other HTTPS requests that use a vault entry set to use only or locked could stop with a TLS error. That is fixed. No action needed.
If you use a vault entry set to use only or locked for git or HTTPS from your workspace, those requests no longer stop halfway with a TLS error. If one failed, run it again. No other action needed.
Some git pushes and clones from a workspace stopped halfway with an error like "GnuTLS recv error (-110): The TLS connection was non-properly terminated". It only affected requests that use a vault entry set to use only or locked. It happened now and then, and more often when the server was busy.
Text version
Your workspace sends a git or HTTPS request that holds only a placeholder. The vault service adds your secret and sends the request to the target. The target answers once and closes its side. The answer travels back through the vault service, and your workspace now always receives all of it.
What happened
The target server closes its side as soon as it has answered. At that moment the answer is still on its way back to you through the vault service. Our side took the closed target for an error and also closed the connection to your workspace, before the rest of the answer had arrived.
What changed
A target that closes now ends only its own side. The connection to your workspace stays open until the whole answer is delivered. Your secret still never reaches your workspace or our main server.
Do I need to do anything?
No. If a push or clone failed with that error, run it again.
Prices, plans and terms did not change.