sqitch-verify - Verify deployed database changes
sqitch [options] verify [<database>] sqitch [options] verify --from-change <change> sqitch [options] verify --to-change <change> sqitch [options] verify --from-change <change> --to-change <change>
Verify that a database is valid relative to the plan and the verification scripts for each deployed change.
verify iterates over all deployed and planned changes (or the subset identified by
--to-change) and checks that each:
Is present in the plan.
Was deployed in the proper order.
Passes its verify test, if one exists and the change has not been reworked.
<database> parameter specifies the database to which to connect, and may also be specified as the
--target option. It can be target name, a URI, an engine name, or plan file path.
Verify tests are scripts that may be associated with each change. If a change has no verify script, a warning is emitted, but it is not considered a failure. If a change has been reworked, only the most recent reworking will have its verify script executed.
Verify scripts should make no assumptions about the contents of the database, as unit tests might. Rather, their job is to ensure that the state of a database is correct after a deploy script has completed. Verify scripts are run through the database engine command-line client, just like deploy and revert scripts. They should cause the client to exit with a non-zero exit code if they fail.
The target database to which to connect. This option can be either a URI or the name of a target in the configuration.
Specify the change with which to start the verification. Defaults to the earliest deployed change. See sqitchchanges for the various ways in which changes can be specified.
Specify the change with which to complete the verification. Defaults to the last deployed change. See sqitchchanges for the various ways in which changes can be specified.
Set a variable name and value for use by the database engine client, if it supports variables. The format must be
--set defuser='Homer Simpson'. Overrides any values loaded from the
A section defining database client variables. Useful if your database engine supports variables in scripts, such as PostgreSQL's
vsqlvariables, MySQL's user variables, and SQL*Plus's
Part of the sqitch suite.