update-deployment

update-deployment 
[-b value | --bootstrap-config=value] 
[-t value | --tool-password=value] 
<-a value | --area=value> 
[-c | --clear] 
[-r value | --remove-packages=value] 
[-v value | --version=value] 
[-d value | --description=value] 
[-f | --force-update] 
[deployment files]

Overview

Use this command to add a new deployment or to update the current deployment in a given area.

Options


Option	Optional or Required	Default Value	Description
`-b value --bootstrap-config=value`	Optional	none	The path to the bootstrap configuration file. See Bootstrap.xml file for more information about this file.
`-t value --tool-password=value`	Optional	none	The configuration tool password used to decrypt the database password in the file bootstrap.xml. If the tool password is omitted, the command prompts the user for it in the console. Refer to Bootstrap.xml file.
`-a value --area=value`	Required	none	The deployment area that should be updated.
`-c --clear`	Optional	none	Indicates that all existing packages should be removed before any new files are added. If no files are provided to add to the deployment, the deployment area is empty.
`-r value --remove-packages=value`	Optional	none	A comma-separated list of IDs of packages that should be removed from the deployment. The IDs can be determined using the show-deployment command. Should not be specified together with the `--clear` argument
`-v value --version=value`	Optional	none	The version of the new deployment. If no value is given, it is taken from the current deployment, or from the last added distribution if one is added.
`-d value --description=value`	Optional	none	The description of the new deployment. If no value is given it is taken from the current deployment, or from the last added distribution if one is added.
`-f --force-update`	Optional	none	Indicates that users connecting to the server should be forced to update their clients.
`[deployment files]`	Optional	none	A comma-separated list of files (packages and distributions) that should be added to the deployment. Note that the paths cannot contain spaces.