You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is one of the cases where the action in the schema is specified as connect.
This means that the request has to be upgraded to a websocket connection. Both sttp ZIO backends supports websockets so this should be simple to implement. Other than that it is structured like a subresource, so the simplest way to add it is to add support for the connect action for subresources and everything else will be generated automatically.
Endpoint:
/api/v1/namespaces/{namespace}/pods/{name}/attach
This is one of the cases where the action in the schema is specified as
connect
.This means that the request has to be upgraded to a websocket connection. Both sttp ZIO backends supports websockets so this should be simple to implement. Other than that it is structured like a subresource, so the simplest way to add it is to add support for the
connect
action for subresources and everything else will be generated automatically.Very similar to #65 and #66.
It is possible to examine how it works with
kubectl attach -v=9
.Example upgrade headers:
Steps to do:
connect
action by using websockets inSubresource
,SubresourceClient
andTestSubresourceClient
classification
andEndpointType
in the code generator, it most likely needs support there tooSubresourceClientGenerator
ClientModuleGenerator
The text was updated successfully, but these errors were encountered: