05 Dec 2021 20:26:51 UTC
- Distribution: App-Sqitch
- Source (raw)
- Browse (raw)
- How to Contribute
- Issues (59)
- KwaliteeBus factor: 2
- 78.74% Coverage
- License: mit
- Perl: v5.10.0
- Activity24 month
- Download (599.4KB)
- MetaCPAN Explorer
- Subscribe to distribution
- This version
- Latest version++ed by:19 non-PAUSE usersDWHEELER David E. Wheelerand 1 contributors
- "iovation Inc., David E. Wheeler"
- Reverse dependencies
- CPAN Testers List
- Dependency graph
sqitch-verify - Verify deployed database changes
sqitch verify [options] [<database>] sqitch verify [options] --from-change <change> sqitch verify [options] --to-change <change> sqitch verify [options] --from-change <change> --to-change <change>
Verify that a database is valid relative to the plan and the verification scripts for each deployed change.
verifyiterates 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
--targetoption. 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 "configuration Variables".
sqitch verify --registry registry
The name of the Sqitch registry schema or database in which sqitch stores its own data.
sqitch verify --client /usr/local/pgsql/bin/psql
Path to the command-line client for the database engine. Defaults to a client in the current path named appropriately for the database engine.
sqitch verify --db-name widgets sqitch verify -d bricolage
Name of the database. In general, targets and URIs are preferred, but this option can be used to override the database name in a target.
sqitch verify --db-username root sqitch verify --db-user postgres sqitch verify -u Mom
User name to use when connecting to the database. Does not apply to all engines. In general, targets and URIs are preferred, but this option can be used to override the user name in a target.
sqitch verify --db-host db.example.com sqitch verify -h appdb.example.net
Host name to use when connecting to the database. Does not apply to all engines. In general, targets and URIs are preferred, but this option can be used to override the host name in a target.
sqitch verify --db-port 7654 sqitch verify -p 5431
Port number to connect to. Does not apply to all engines. In general, targets and URIs are preferred, but this option can be used to override the port in a target.
sqitch verify --plan-file my.plan
Path to the deployment plan file. Overrides target, engine, and core configuration values. Defaults to $top_dir/sqitch.plan.
A section defining database client variables. The
deploy.variablesconfiguration is read from the
deploycommand configuration, on the assumption that the values will generally be the same on verify. If they're not, use
These variables are useful if your database engine supports variables in scripts, such as PostgreSQL's
vsqlvariables, MySQL's user variables, SQL*Plus's
DEFINEvariables, and Snowflake's SnowSQL variables.
May be overridden by
--setor target and engine configuration. Variables are merged in the following priority order:
Part of the sqitch suite.