Binary Delete

The Binary Delete component allows you to delete binaries from the Content Store.

The binaries are deleted from the binaries.files and binaries.chunks collections.

It uses either the source.localReference or target.localReference value from the incoming message to delete a binary.

See how it works:
Binary Delete Explainer

note

Also covered in the Content Store overview video:
Watch video

Configuration

Connection string

A MongoDB connection string.

Example: mongodb://<username>:<password>@localhost:27017/<databaseName>

Here <databaseName> is the database to delete the binary from.

Use TLS

Enables TLS for your mongoDB connection.

Allow Invalid Certificates

Checking this will disable certificate validation. Warning: specifying this option in a production environment makes your application insecure and potentially vulnerable to expired certificates and to foreign processes posing as valid client instances.

Certificate Authority File

One or more certificate authorities to trust when making a TLS connection.

Example: .\ca.pem

Delete reference

Source: Delete binary based on the source.localReference value.

Target: Delete binary based on the target.localReference value.

Inputs | Outputs

Binary Delete

Input

Output

Error

00 0 (ilyigtz4d)

The component will look on the incoming data for the source.localReference or target.localReference key and uses that to delete the binary from the binaries GridFS bucket since it references the_id field of the binary. The binary in the Content Store matching this reference will be deleted.

Example:

{
    "source": {
    "localReference": "6232dea643dbbf33e0906e85"
    }

}