dtm verify checks the following:
1 Config File¶
dtm verify first verifies if the config file can be loaded successfully.
If not, the following information might be printed out:
- if the config file doesn't exist, it reminds you if you forgot to specify the config file by using the "-f" parameter;
- if the config format isn't correct, it would print some error.
dtm verify then checks if all required plugins (according to the config file) exist.
If not, it tries to give you a hint that maybe you forgot to run
dtm init first.
dtm verify also tries to create a state manager that operates a backend. If something is wrong with the state, it generates an error telling you what exactly the error is.
4 Config / State / ResourceStatus¶
For definitions of Config, State, and ResourceStatus, see Core Concepts.
dtm verify tries to see if the Config matches the State and the Resource or not. If not, it tells you what exactly is not the same, and what would happen if you run
If all the above checks are successful,
dtm verify finishes with a success log "Verify succeeded."
||The path to the config file.|
||The path to plugins.|