Location string   `xml:"LocationConstraint"`
}

// DeleteObjectsRequest - xml carrying the object key names which needs to be deleted.
type DeleteObjectsRequest struct {
	// Element to enable quiet mode for the request
	Quiet bool
	// List of objects to be deleted
	Objects []ObjectToDelete `xml:"Object"`

        // For each of 4 indices: delete old + delete backup = 8 deletes
        assertEquals(8, testClient.deletedIndices.size());
        // Verify original index names appear in deleted list (old index deletion at step 3)
        boolean foundOriginalDelete = false;
        for (final String deleted : testClient.deletedIndices) {
            if (!deleted.contains(".backup.") && !deleted.contains(".rebuild.")) {

		objectsAfterDelete []string
	}{
		// Test 1: removes an object and checks it is the only object
		// that has been deleted.
		{
			"bucket1",
			[]objectUpload{{"object0", "content"}, {"object1", "content"}},
			"object0",
			[]string{"object1"},
		},
		// Test 2: remove an object inside a directory and checks it is deleted
		// with its parent since this former becomes empty
		{
			"bucket2",

        Path tempFile = Files.createTempFile("toctou_test", ".tmp");
        try {
            assertTrue(Files.exists(tempFile));

            boolean deleted = Files.deleteIfExists(tempFile);

            assertTrue(deleted);
            assertFalse(Files.exists(tempFile));
        } finally {
            Files.deleteIfExists(tempFile);
        }
    }

    @Test

   *
   * <p><b>Warning:</b> On a file system that supports symbolic links, it is possible for an
   * insecure recursive delete to delete files and directories that are <i>outside</i> the directory
   * being deleted. This can happen if, after checking that a file is a directory (and not a
   * symbolic link), that directory is deleted and replaced by a symbolic link to an outside

success.delete_doc_from_index = Started a process to delete documents from an index.
success.crawling_info_delete_all = Deleted session data.
success.start_crawl_process = Started a crawl process.
success.upload_design_file = Updated {0}.
success.update_design_jsp_file = Updated {0}.
success.create_crawling_config_at_wizard = Created a crawling config {0}.
success.failure_url_delete_all = Deleted failure URLs.
success.delete_file = Deleted {0} file.

success.delete_doc_from_index = Started a process to delete documents from an index.
success.crawling_info_delete_all = Deleted session data.
success.start_crawl_process = Started a crawl process.
success.upload_design_file = Updated {0}.
success.update_design_jsp_file = Updated {0}.
success.create_crawling_config_at_wizard = Created a crawling config {0}.
success.failure_url_delete_all = Deleted failure URLs.
success.delete_file = Deleted {0} file.

            .collect(Collectors.toCollection(TreeSet::new));

        if (filesToDelete.isEmpty()) {
            LOGGER.warn("No files need to be deleted.");
            return;
        }

        LOGGER.warn("The following changelog files {} be deleted:", dryRun ? "can" : "will");
        LOGGER.warn("");
        filesToDelete.forEach(file -> LOGGER.warn("\t{}", rootDir.relativize(file.toPath())));

		case objectlock.RetGovernance:
			// In governance mode, users can't overwrite or delete an object
			// version or alter its lock settings unless they have special
			// permissions. With governance mode, you protect objects against
			// being deleted by most users, but you can still grant some users
			// permission to alter the retention settings or delete the object
			// if necessary. You can also use governance mode to test retention-period

case of versioned deletes a.k.a permanent delete of a version by doing a `mc rm --version-id` on a object, replication implementation marks a object version permanently deleted as `PENDING` purge and deletes the version from source after syncing to the target and ensuring target version is deleted. The delete marker being deleted or object version being deleted will still be visible on listing with `mc ls --versions` until the sync is completed. Objects marked as deleted will not be accessible via `GET`...