Package com.viam.service.shell.v1

Class ShellServiceGrpc.ShellServiceBlockingV2Stub

java.lang.Object
io.grpc.stub.AbstractStub<ShellServiceGrpc.ShellServiceBlockingV2Stub>
io.grpc.stub.AbstractBlockingStub<ShellServiceGrpc.ShellServiceBlockingV2Stub>
com.viam.service.shell.v1.ShellServiceGrpc.ShellServiceBlockingV2Stub
Enclosing class:
ShellServiceGrpc
public static final class ShellServiceGrpc.ShellServiceBlockingV2Stub extends io.grpc.stub.AbstractBlockingStub<ShellServiceGrpc.ShellServiceBlockingV2Stub>
A stub to allow clients to do synchronous rpc calls to service ShellService. 
 A ShellService service allows access to an interactive shell experience, including
 utilities commonly found in tandem with other secure shells.

  • Method Details

    • build

      protected ShellServiceGrpc.ShellServiceBlockingV2Stub build(io.grpc.Channel channel, io.grpc.CallOptions callOptions)
      Specified by:
      build in class io.grpc.stub.AbstractStub<ShellServiceGrpc.ShellServiceBlockingV2Stub>

    • shell

      @ExperimentalApi("https://github.com/grpc/grpc-java/issues/10918") public io.grpc.stub.BlockingClientCall<Shell.ShellRequest,Shell.ShellResponse> shell()
       Shell starts a shell with an input and output pipe.

    • copyFilesToMachine

      @ExperimentalApi("https://github.com/grpc/grpc-java/issues/10918") public io.grpc.stub.BlockingClientCall<Shell.CopyFilesToMachineRequest,Shell.CopyFilesToMachineResponse> copyFilesToMachine()
       CopyFilesToMachines copies a stream of files from a client to the connected-to machine.
 Initially, metadata is sent to describe the destination in the filesystem in addition
 to what kind of file(s) are being sent.
 Once metadata is sent, the file transfer can proceed where one-by-one, file data is sent
 until EOF per file.
 After each file is sent, the machine must respond with an ACK before the next file can
 be sent. This provides back-pressure and ordering.
 The order in which individual files are sent does not matter; that is, if traversing a
 directory, copying depth-first, breadth-first, or any other algorithm does not matter.
 Permissions and metadata on files copied are only preserved if the preserve option is
 set in the initial request metadata.

    • copyFilesFromMachine

      @ExperimentalApi("https://github.com/grpc/grpc-java/issues/10918") public io.grpc.stub.BlockingClientCall<Shell.CopyFilesFromMachineRequest,Shell.CopyFilesFromMachineResponse> copyFilesFromMachine()
       CopyFilesFromMachine copies a stream of files from a connected-to machine to the calling client.
 Essentially, it is the inverse of CopyFilesToMachine with the same ACK mechanism in reverse.
 The initial metadata request will request the paths to copy along with if permissions should
 be preserved (and consequently sent over the wire).

    • doCommand

      public Common.DoCommandResponse doCommand(Common.DoCommandRequest request) throws io.grpc.StatusException
       DoCommand sends/receives arbitrary commands
      Throws:
      io.grpc.StatusException