Generate code with protobuf and csi-proxy-api-gen for RmdirContents

client/api/filesystem/v2alpha1/api.proto

@@ -15,6 +15,9 @@ service Filesystem {
     // This may be used for unlinking a symlink created through CreateSymlink.
     rpc Rmdir(RmdirRequest) returns (RmdirResponse) {}
 
+    // RmdirContents removes the contents of a directory in the host filesystem.
+    rpc RmdirContents(RmdirContentsRequest) returns (RmdirContentsResponse) {}
+
     // CreateSymlink creates a symbolic link called target_path that points to source_path
     // in the host filesystem (target_path is the name of the symbolic link created,
     // source_path is the existing path).
@@ -86,6 +89,29 @@ message RmdirResponse {
     // Intentionally empty.
 }
 
+message RmdirContentsRequest {
+    // The path whose contents will be removed in the host's filesystem.
+    // All special characters allowed by Windows in path names will be allowed
+    // except for restrictions noted below. For details, please check:
+    // https://docs.microsoft.com/en-us/windows/win32/fileio/naming-a-file
+    //
+    // Restrictions:
+    // Only absolute path (indicated by a drive letter prefix: e.g. "C:\") is accepted.
+    // Depending on the context parameter of this function, the path prefix needs
+    // to match the paths specified either as kubelet-csi-plugins-path
+    // or as kubelet-pod-path parameters of csi-proxy.
+    // UNC paths of the form "\\server\share\path\file" are not allowed.
+    // All directory separators need to be backslash character: "\".
+    // Characters: .. / : | ? * in the path are not allowed.
+    // Path cannot be a file of type symlink.
+    // Maximum path length will be capped to 260 characters.
+    string path = 1;
+}
+
+message RmdirContentsResponse {
+    // Intentionally empty.
+}
+
 message CreateSymlinkRequest {
     // The path of the existing directory to be linked.
     // All special characters allowed by Windows in path names will be allowed