Secrets

Tag 14: the client feeds the container the values of its secrets, each by name, before its next MCP exchange; the server opens a secrets channel on the container’s begin scope with the values verbatim and relays exactly one channel response, fed or the container’s refusal, and the channel response finish.

The client opens this channel to hand the container the values of the secrets its program declared, one value under every name, before the container is next delivered an MCP exchange. The server opens a secrets channel on the begin scope of the container’s proxy with the values and relays the answer the proxy gives. Until the proxy has answered Fed, the proxy delivers no exchange to a program that declared a secret, as the begin response states; an exchange opened meanwhile is held.

• The request. The tag byte 14 followed by the values as JSON. Request states its form.
• The response. Exactly one channel response, relayed as the proxy sent it, and the channel response finish. Response states the sequence.
• When. The first values of a run are not fed on this channel: the server feeds them itself, from the answer to the registration channel, before it sends the id. After every Inactive of the main stream the container holds no values, and the client feeds them again on this channel before the next exchange.
• Verbatim. The server relays the values as the client sent them and reads none of them. A value is read by nothing between the client and the container’s program.