DCT Toolkit release notes | Data Control Tower 2026.5

Toolkit versioning and release notes apply only to the dct-toolkit wrapper application itself. New commands and in-application documentation are dynamically updated when DCT is upgraded and do not require a toolkit version bump.

New features

Version 1.5.4

Upload and download commands

Added support for upload and download commands.

Example 1:

./dct-toolkit upload_synthetic_file file='<path/to/csv>'

Output:

file:
  id: "eb1322b7-c8cd-4dd8-a382-1d59099dc8c1"
  file_name: "download.csv"
  file_checksum: "4fbdfec67834d24ce7375cef4ff13f5089c67dbb750539256f33b5af266ca2bd"
  creation_date: "2026-09-04T05:53:02.028516637Z"
  account_id: 2
  tags: []

Example 2:

./dct-toolkit download_rule_set_export rule_set_id=1a1a9099-bd77-4bb9-b0bc-edae8cb1902e format=csv --output=/tmp/ruleset.csv

Example 3:

./dct-toolkit upload_masking_file_fixture --help
Usage: dct-toolkit upload_masking_file_fixture [-hV] [--no-wait] [--overwrite]
       [description=string] file=<path> [-jp=<jsonPath> | -ex=<expand>] [-A |
       -c=<columnsList>[,<columnsList>...] [-c=<columnsList>[,
       <columnsList>...]]... | -js]

Description
Synthetic multipart upload with a binary property and a metadata property.

Required Arguments
      file=<path>          Local file path for the file part.

Optional Arguments
      description=string
      --overwrite

Fixed an issue in which the dct-toolkit fetch_table_names command returned null.
Fixed an issue in which the dct-toolkit sync_synthetic_application command returned null.
Fixed an issue that prevented dct-toolkit from running on very old CPUs.

Version 1.5.3

Version 1.5.3 was not publicly released. It remained in pre-release and was superseded by version 1.5.4.

Version 1.5.2

DCT Toolkit documentation improvements

DCT Toolkit has been overhauled to make it easier to learn and use. Within the CLI itself, command help is reorganized: commands now carry summaries and descriptions, groups and arguments are ordered logically, and required versus optional fields are clearly distinguished.

Alongside this, the published toolkit documentation has been rebuilt with a new getting-started guide, a broader set of worked examples, and a dedicated reference mapping DX toolkit commands to their DCT toolkit equivalents. See more in the DCT Toolkit topics.

Version 1.5.1

Version 1.5.1 was not publicly released. It remained in pre-release and was superseded by version 1.5.2.

Version 1.5.0

dct-toolkit for DCT appliance instances

dct-toolkit now works out of the box for DCT appliance instances. Before, users had to append /dct in the dctUrl configuration property. Now, it's automatically handled by dct-toolkit. Just provide the host and port details, then dct-toolkit will infer the correct URL to use for DCT APIs. Valid values for dctUrl configuration properties are:
- <https://<host>>:<port>
- <https://<host>>:<port>/dct
This applies to standalone DCT deployments and DCT appliance versions of dct-toolkit 1.5.0. dct-toolkit will (by default) always use HTTPS for consuming DCT APIs. A valid value for the dctUrl configuration property could be simply <host>:<port>.

Verification of configuration properties

dct-toolkit will always verify configuration properties before saving, generating helpful error messages to diagnose connection problems.

If the insecureSSL property is not set to true and correct CA certificates are not provided, dct-toolkit fails with an error message:

./dct-toolkit create_config dctUrl="dct-appliance-aws.dlpxdc.co" apiKey=<api key value>
								Verifying config properties...
							SSL exception. Make sure DCT has been configured for HTTPS or bypass SSL certificate validation with the --insecureSSL config property or by setting the DCT_TOOLKIT_SSL_INSECURE environment variable

If the DCT host is not reachable, dct-toolkit fails with an error message:

./dct-toolkit create_config dctUrl="dct-appliance-awss.dlpxdc.co" apiKey=<api key value> --insecureSSL
								Verifying config properties...
							Cannot resolve host with url : dct-appliance-awss.dlpxdc.co. Please check DNS or firewall settings to confirm the host URL is reachable.

If DCT is not running at the configured port, dct-toolkit fails with an error message:

./dct-toolkit create_config dctUrl="dct-appliance-aws.dlpxdc.co:444" apiKey=<api key value> --insecureSSL
								Verifying config properties...
							Cannot connect to host url : dct-appliance-aws.dlpxdc.co:444. Please check the DCT URL and confirm that DCT is running and accepting HTTPS connections.

Version 1.4.0

Enhanced search experience
Users can now employ the search command with a more straightforward syntax, in addition to the existing option for filter_expression use. This command structure will search for VDBs that have a name matching <vdb_name> and database type matching <database_type>:
```
./dct-toolkit search_vdb name "<vdb_name>" database_type <database_type>
```
The name flag allows users to specify the VDB name, while the database_type flag lets them indicate the database type.

Simplified syntax for value array input
Users can now provide array values using more natural and versatile formats, such as comma-separated values or repeated options. To include a comma within a value, escape it with a backslash.
- Comma-separated values
```
vdb_ids=VCDO_ZKJ,ABCD_JHI
```
- Repeated options
```
vdb_ids=ABCD_JHI vdb_ids=XYZ_ABC
```
- Escaped commas inside values
```
vdb_ids=VCDO_ZKJ,\"AB,CD_JHI\"
```
This feature is not backward compatible with previous versions. The older string format for array input is no longer supported:
```
vdb_ids='["VCDO_ZKJ", "ABCD_JHI"]'
```
This applies to all options where the type is an array of values.

Version 1.2.0

--json/-js option
dct-toolkit now supports a --json/-js option for all commands. If specified, all properties from the DCT response are printed in JSON format. This option is mutually exclusive with --all-columns/-A and --columns/-c but can be used with --jsonpath/-jp and --expand/-ex.
--csv/-cs option
dct-toolkit now supports a --csv/-cs option for all commands. If specified, all properties from the DCT response are printed in CSV format. This option can be used with --columns/-c to output specific properties, and with --jsonpath/-jp and --expand/-ex.
- This option is only applicable to list API responses rendered in table format by default. For APIs returning a single object, this option is ignored.
create_config and encrypt_api_key commands are now interactive

When providing an apiKey value with create_config or encrypt_api_key, there is a risk that the plaintext key can leak via shell history. Both commands are now interactive — providing an API key interactively prevents it from appearing in shell history. Once the following commands are executed, dct-toolkit will prompt for the API key before proceeding. The DCT instance URL must include the protocol and suffix (for example, https://dct.company.co/dct/).
```
./dct-toolkit encrypt_api_key dctUrl=<DCT instance URL> apiKey
					./dct-toolkit create_config dctUrl=<DCT instance URL> apiKey
```

Last updated

Oct 8, 2026

Release notes