There are several sub-commands that need to be implemented
emctl delete sub-command, (you can implement it by referring #22
emctl delete -f <location>, support -f arguments which specify a location contains EaseMesh spec files, the location could be directory, URL, and stdin/stdout
emctl delete <kind> <name_of_resource> , support delete a specified resource of the kind, kind could be [1]
emctl get sub-command
emctl get <kind> [name_of_resource] [-o yaml/json] support query a specified resource. kind could be [1],name_of_resource` is resource name. The output can be a spec in yaml or json language, If -o argument is omitted, just list specified kind of resources in a table like below:
Kind ResourceName Created
-----------------------------------------------------------------
resilience customers 2021/06/25Z01:01:01.333
zhao-kun
commented
3 years ago
There are several sub-commands that need to be implemented
emctl delete sub-command, (you can implement it by referring #22
emctl delete -f <location>, support -f arguments which specify a location contains EaseMesh spec files, the location could be directory, URL, and stdin/stdoutemctl delete <kind> <name_of_resource>, support delete a specified resource of the kind, kind could be [1]emctl get sub-command
emctl get <kind> [name_of_resource] [-o yaml/json] support query a specified resource. kind could be [1],name_of_resource` is resource name. The output can be a spec in yaml or json language, If -o argument is omitted, just list specified kind of resources in a table like below:[1] https://github.com/megaease/easemesh/blob/main/ctl/cmd/client/resource/types.go#L19