deptool deploy¶

deptool deploy [--no-confirm] [--plan-only]
               [--app <apps>]... [--host <hosts>]...
               [--] [<dir>]

Description¶

Read the config tree in directory <dir> and deploy it to the cluster defined in there. This first computes the plan, which happens completely offline. Then it prompts for confirmation before deploying to the affected hosts. See the deployment phases reference for details on how the deployment proceeds.

By convention, the directory <dir> is named after the cluster, e.g. staging or prod. See the directory layout reference for how <dir> should be structured. It is possible for multiple clusters to share a store, as long as the hosts have no overlap.

When you provide <dir> explicitly, Deptool saves it to the config file in the store. On a subsequent run, you can omit <dir>, and Deptool will use the last-used one.

Options¶

--no-confirm¶

By default Deptool prompts for confirmation after presenting the deployment plan. With this flag, it instead proceeds automatically.

--plan-only¶

Compute the plan and exit, do not connect to any host.

--app <apps>¶

Limit the apps to deploy. Can be provided multiple times, and supports a comma-separated list of apps too. Can be combined with --host to further limit the hosts to deploy to.

When an app filter is in effect, Deptool leaves excluded apps untouched, even when they do have changes in the config tree. When an app is currently deployed to a host, but removed from the config tree, selecting it with --app deploys the removal.

When an app filter is in effect, Deptool does not inspect the directories in the config tree for excluded apps, so that a syntax error in a manifest for one app does not prevent deploying a different app with --app.

--host <hosts>¶

Limit the hosts to deploy to. Can be provided multiple times, and supports a comma-separated list of hosts too. For example, in a cluster with hosts web1 through web5, passing --host web1,web2 --host web3 would exclude web4 and web5 from the deploy. Can be combined with --app to further limit the apps to deploy on the selected hosts.

When a host filter is in effect, Deptool does not inspect the directories in the config tree for excluded hosts, so that e.g. a syntax error in a manifest for one host does not prevent deploying to a different host with --host.