dtm delete
1 Normal (Non-Force) Delete
When deleting using dtm delete
, here’s what happens:
- Read the Config
- For each Tool defined in the Config, if there is a corresponding State, the
Delete
interface will be called.
Note: the Delete
change will be executed only if the _State exists._
2 Force Delete
When deleting using dtm delete --force
, here’s what happens:
- Read the Config
- The
Delete
interface will be called for each Tool defined in the Config.
Note: the difference between “force delete” and “normal delete” is that in force mode, no matter the _State exists or not, dtm
will try to trigger the Delete
interface. The purpose is for corner cases where the state gets corrupted or even lost during testing (I hope this only happens in the development environment), there is still a way to clean up the Tools._
3 Flags
Short | Long | Default | Description |
---|---|---|---|
—force | false | Force delete by config. | |
-f | —config-file | “config.yaml” | The path to the config file. |
-d | —plugin-dir | “~/.devstream/plugins” | The path to plugins. |
-y | —yes | false | Delete directly without confirmation. |