MinIO icon

MinIO

Connect to your MinIO server

Actions11

Overview

This node is designed to remove an object from a specified bucket in a storage service compatible with the MinIO API. It is useful in scenarios where you need to programmatically delete files or objects stored in cloud buckets, such as cleaning up outdated data, removing temporary files, or managing storage space.

For example, you might use this node to delete a specific image file from a media bucket after processing it, or to remove backup files that are no longer needed.

Properties

Name Meaning
Bucket Name The name of the bucket containing the object to be removed. Can be selected from a list of existing buckets or provided as a string ID.
Object Name The name (key) of the object within the bucket to delete. Can be selected from a list of objects or provided as a string ID.
Options Additional options for removal:
- versionId: Specify a version of the object to delete.
- governanceBypass: Boolean to bypass governance retention if applicable.

Output

The node outputs JSON data representing the result of the remove operation. Typically, this will confirm whether the deletion was successful or provide details about the operation's outcome.

If the underlying service supports versioning or governance policies, the output may reflect those aspects based on the options used.

No binary data output is expected from this node since its purpose is deletion.

Dependencies

  • Requires connection to a MinIO-compatible storage service.
  • Needs appropriate credentials with permissions to delete objects from the specified bucket.
  • The node relies on internal methods for listing buckets and objects to support resource locators.
  • No additional external dependencies beyond the configured storage service and authentication.

Troubleshooting

  • Common Issues:

    • Attempting to delete an object that does not exist will likely result in an error.
    • Insufficient permissions can cause authorization errors.
    • Providing incorrect bucket or object names will prevent successful deletion.
    • If versioning is enabled on the bucket, omitting the correct version ID when required may lead to unexpected results.

  • Error Messages:

    • "Object not found": Verify the bucket and object names are correct.
    • "Access denied" or "Unauthorized": Check that the API key or credentials have delete permissions.
    • "Version ID invalid": Ensure the version ID provided matches an existing version of the object.

Resolving these typically involves verifying input parameters, checking credentials, and confirming the object's existence.

Links and References

Discussion