FilesystemService
This page lists the methods of FilesystemService in kibotos.ctrl.v1 with the messages and enums each one uses, generated from ctrl.proto and its comments. Those that several services use are on kibotos.ctrl.v1 types.
endpoint of a data-plane session, with its credential in Authorization: Bearer.How to call itFilesystemService performs metadata operations on the Workspace filesystem: stat, listing, directory creation, move, removal, and directory watching. File content is read and written through the /v1/files HTTP endpoint on the same data-plane listener. Stat, ListDir and WatchDir require FILE_READ; the rest require FILE_WRITE. A path, here and on /v1/files, is absolute or relative to the home directory of the identity user selects; responses always name entries by their cleaned absolute path.
Stat
/kibotos.ctrl.v1.FilesystemService/StatUnaryListDir
/kibotos.ctrl.v1.FilesystemService/ListDirUnaryListDirRequestListDirResponseMakeDir
/kibotos.ctrl.v1.FilesystemService/MakeDirUnaryMove
/kibotos.ctrl.v1.FilesystemService/MoveUnaryMoveRequestuser selects the identity the operation runs as: empty for the Template default, the declared account name, or root.
MoveResponseRemove
/kibotos.ctrl.v1.FilesystemService/RemoveUnaryWatchDir
WatchDir reports changes to the entries of one directory. It sends started once the watch is in place; from then on every change yields at least one event or the stream ends with RESOURCE_EXHAUSTED. Events only say which path may have changed: callers list the directory after started and again after the stream ends. The stream never ends with OK. The server announces it as workspace.filesystem.watch_dir.
/kibotos.ctrl.v1.FilesystemService/WatchDirServer streamingWatchDirRequestpath names the directory to watch. A symbolic link to a directory is followed; event paths stay under the requested path.
include_entry attaches the affected entry to CREATE, WRITE and CHMOD events while the entry still exists.
user selects the identity the operation runs as: empty for the Template default, the declared account name, or root. The identity must be able to read the directory.
WatchDirResponse- One of
event
WatchDirStartedEvent
WatchDirStartedEvent is the first message of every watch stream.
This message has no fields.
WatchDirHeartbeatEvent
This message has no fields.
FilesystemEvent
FilesystemEvent reports that one entry of the watched directory may have changed. Changes inside subdirectories are not reported.
path is the cleaned absolute path of the entry: the requested directory joined with the entry name.
FilesystemEventType
FILESYSTEM_EVENT_TYPE_UNSPECIFIED= 0FILESYSTEM_EVENT_TYPE_CREATE= 1CREATE: the entry was created or moved into the directory.
FILESYSTEM_EVENT_TYPE_WRITE= 2WRITE: the file content was written.
FILESYSTEM_EVENT_TYPE_REMOVE= 3REMOVE: the entry was deleted.
FILESYSTEM_EVENT_TYPE_RENAME= 4RENAME: the entry was moved away; path is where it was.
FILESYSTEM_EVENT_TYPE_CHMOD= 5CHMOD: permissions, ownership, timestamps or another attribute changed.
Messages and enums
Several methods of FilesystemService use these messages and enums.
EntryInfo
EntryInfo describes one filesystem entry without following a trailing symbolic link.
path is the cleaned absolute path of the entry.
size_bytes is meaningful for regular files only and is zero otherwise.
mode carries permission bits only.
EntryType
ENTRY_TYPE_UNSPECIFIED= 0ENTRY_TYPE_FILE= 1ENTRY_TYPE_DIRECTORY= 2ENTRY_TYPE_SYMLINK= 3ENTRY_TYPE_OTHER= 4
ServiceConnectionService
This page lists the methods of ServiceConnectionService in kibotos.ctrl.v1 with the messages and enums each one uses, generated from ctrl.proto and its comments. Those that several services use are on kibotos.ctrl.v1 types.
ProcessService
This page lists the methods of ProcessService in kibotos.ctrl.v1 with the messages and enums each one uses, generated from ctrl.proto and its comments. Those that several services use are on kibotos.ctrl.v1 types.