Delete command
The following delete commands are available:
Note: These commands are available with DBB 2.0.2 and later. If you have DBB 2.0.0 or 2.0.1, see Legacy commands.
Delete group
This command deletes a build group from the metadata store.
Usage
dbb delete group <groupName> [options]
Positional arguments
groupNamefor the name of the build group
Command Options
- None
Configuration options
Note that you can omit the configuration options if the CLI session is started and active.
You can specify the following options:
-
--typefor the metadata store implementation type. The possible values arefile(default) anddb2. -
--locationfor the location of the file system implementation. The default value is$HOME. -
--userfor the Db2® connection user ID. -
--passwordfor the Db2 connection password.
IMPORTANT: The password must be encrypted with the DBB password utility. See Encrypting metadata store passwords. -
--password-filefor the location of Db2 connection password that is stored in a password file.
IMPORTANT: The password file contains an encrypted password and must be generated with the DBB password utility. See Encrypting metadata store passwords. -
--urlfor the Db2 server location. It can be local or a remote URL. It is optional if the URL is provided in the--db2_configfile. -
--db2-configfor the location of the Db2 connection configuration file.
Delete collection
This command deletes a collection in a build group from the metadata store.
Usage
dbb delete collection <groupName> <collectionName> [options]
Positional arguments
groupNamefor the name of the build group with the collectioncollectionNamefor the name of the collection
Command Options
- None
Configuration options
Note that you can omit the configuration options if the CLI session is started and active.
You can specify the following options:
-
--typefor the metadata store implementation type. The possible values arefile(default) anddb2. -
--locationfor the location of the file system implementation. The default value is$HOME. -
--userfor the Db2® connection user ID. -
--passwordfor the Db2 connection password.
IMPORTANT: The password must be encrypted with the DBB password utility. See Encrypting metadata store passwords. -
--password-filefor the location of Db2 connection password that is stored in a password file.
IMPORTANT: The password file contains an encrypted password and must be generated with the DBB password utility. See Encrypting metadata store passwords. -
--urlfor the Db2 server location. It can be local or a remote URL. It is optional if the URL is provided in the--db2_configfile. -
--db2-configfor the location of the Db2 connection configuration file.
Delete result
This command deletes a build result in a build group from the metadata store.
Usage
dbb delete result <groupName> <resultName> [options]
Positional arguments
groupNamefor the name of the build group with the build resultresultNamefor the name of the build result
Command Options
- None
Configuration options
Note that you can omit the configuration options if the CLI session is started and active.
You can specify the following options:
-
--typefor the metadata store implementation type. The possible values arefile(default) anddb2. -
--locationfor the location of the file system implementation. The default value is$HOME. -
--userfor the Db2® connection user ID. -
--passwordfor the Db2 connection password.
IMPORTANT: The password must be encrypted with the DBB password utility. See Encrypting metadata store passwords. -
--password-filefor the location of Db2 connection password that is stored in a password file.
IMPORTANT: The password file contains an encrypted password and must be generated with the DBB password utility. See Encrypting metadata store passwords. -
--urlfor the Db2 server location. It can be local or a remote URL. It is optional if the URL is provided in the--db2_configfile. -
--db2-configfor the location of the Db2 connection configuration file.
Delete file
This command deletes a logical file in a collection from the metadata store.
Usage
dbb delete file <groupName> <collectionName> <fileName> [options]
Positional arguments
groupNamefor the name of the build group with the specified collectioncollectionNamefor the name of the collection with the logical filefileNamefor the name of the logical file
Command Options
- None
Configuration options
Note that you can omit the configuration options if the CLI session is started and active.
You can specify the following options:
-
--typefor the metadata store implementation type. The possible values arefile(default) anddb2. -
--locationfor the location of the file system implementation. The default value is$HOME. -
--userfor the Db2® connection user ID. -
--passwordfor the Db2 connection password.
IMPORTANT: The password must be encrypted with the DBB password utility. See Encrypting metadata store passwords. -
--password-filefor the location of Db2 connection password that is stored in a password file.
IMPORTANT: The password file contains an encrypted password and must be generated with the DBB password utility. See Encrypting metadata store passwords. -
--urlfor the Db2 server location. It can be local or a remote URL. It is optional if the URL is provided in the--db2_configfile. -
--db2-configfor the location of the Db2 connection configuration file.
Delete map
This command deletes a build map in a build group from the metadata store.
Usage
dbb delete map <groupName> <mapName> [options]
Positional arguments
groupNamefor the name of the build group with the build mapmapNamefor the name of the build map
Command Options
- None
Configuration options
Note that you can omit the configuration options if the CLI session is started and active.
You can specify the following options:
-
--typefor the metadata store implementation type. The possible values arefile(default) anddb2. -
--locationfor the location of the file system implementation. The default value is$HOME. -
--userfor the Db2® connection user ID. -
--passwordfor the Db2 connection password.
IMPORTANT: The password must be encrypted with the DBB password utility. See Encrypting metadata store passwords. -
--password-filefor the location of Db2 connection password that is stored in a password file.
IMPORTANT: The password file contains an encrypted password and must be generated with the DBB password utility. See Encrypting metadata store passwords. -
--urlfor the Db2 server location. It can be local or a remote URL. It is optional if the URL is provided in the--db2_configfile. -
--db2-configfor the location of the Db2 connection configuration file.