David E. Wheeler > App-Sqitch-0.973 > sqitch-checkout

Download:
App-Sqitch-0.973.tar.gz

Annotate this POD

Website

View/Report Bugs
Source   Latest Release: App-Sqitch-0.992

Name ^

sqitch-checkout - Revert, checkout another VCS branch, and re-deploy changes

Synopsis ^

  sqitch [options] checkout <branch>

Description ^

Checkout another branch in your project's VCS (such as git), while performing the necessary database changes to update your database for the new branch.

More specifically, the checkout command compares the plan in the current branch to that in the target branch, identifies the last common changes between them, reverts to that change as if sqitch revert was called (unless there have been no changes deployed since that change), checks out the target branch, and then deploys all changes in the new branch as if sqitch deploy had been called.

If the VCS is already on the target branch, nothing will be done.

Options ^

--mode

Specify the reversion mode to use in case of failure. Possible values are:

all

In the event of failure, revert all deployed changes, back to the point at which deployment started. This is the default.

tag

In the event of failure, revert all deployed changes to the last successfully-applied tag. If no tags were applied during this deployment, all changes will be reverted to the point at which deployment began.

change

In the event of failure, no changes will be reverted. This is on the assumption that a change is atomic, and thus may may be deployed again.

--verify

Verify each change by running its verify script, if there is one. If a verify test fails, the deploy will be considered to have failed and the appropriate reversion will be carried out, depending on the value of --mode.

--no-verify

Don't verify each change. This is the default.

-s
--set

Set a variable name and value for use by the database engine client, if it supports variables. The format must be name=value, e.g., --set defuser='Homer Simpson'. Overrides any values loaded from the deploy.variables or revert.variables configurations.

-d
--set-deploy

Set a variable name and value for use by the database engine client when deploying, if it supports variables. The format must be name=value, e.g., --set defuser='Homer Simpson'. Overrides any values from --set or loaded from the deploy.variables configuration.

-r
--set-revert

Sets a variable name to be used by the database engine client during when reverting, if it supports variables. The format must be name=value, e.g., --set defuser='Homer Simpson'. Overrides any values from --set or loaded from the deploy.variables and revert.variables configurations.

--log-only

Log the changes as if they were deployed, but without actually running the deploy scripts. Useful for an existing database that is being converted to Sqitch, and you need to log changes as deployed because they have been deployed by other means in the past.

-y

Disable the prompt that normally asks whether or not to execute the revert.

Configuration Variables ^

[deploy.variables]
[revert.variables]

A section defining database client variables. The deploy.variables configuration is read from the deploy command configuration, on the assumption that the values will generally be the same. If they're not, use revert.variables to override deploy.variables.

These variables are Useful if your database engine supports variables in scripts, such as PostgreSQL's psql variables.

checkout.verify
deploy.verify

Boolean indicating whether or not to verify each change after deploying it.

checkout.mode
deploy.mode

Deploy mode. The supported values are the same as for the --mode option.

[checkout.no_prompt]
[revert.no_prompt]

A boolean value indicating whether or not to disable the prompt before executing the revert. The checkout.no_prompt variable takes precedence over revert.no_prompt, and both may of course be overridden by -y.

Sqitch ^

Part of the sqitch suite.

syntax highlighting: