// Default constructor with explicit documentation
    }

    /**
     * The name of the plugin to delete.
     * Required field with maximum length of 100 characters.
     */
    @Required
    @Size(max = 100)
    public String name;

    /**
     * The version of the plugin to delete.
     * Optional field with maximum length of 100 characters.
     */
    @Size(max = 100)
    public String version;

		if err != nil {
			continue
		}
		err = loadMRF(rc, m.opCh)
		if err != nil {
			continue
		}
		// finally delete the file after processing mrf entries
		localDrive.Delete(GlobalContext, minioMetaBucket, pathJoin(healMRFDir, "list.bin"), DeleteOptions{})
		break
	}
}

var healSleeper = newDynamicSleeper(5, time.Second, false)

		"Total cluster objects count")
	usageVersionsCountMD = NewGaugeMD(usageVersionsCount,
		"Total cluster object versions (including delete markers) count")
	usageDeleteMarkersCountMD = NewGaugeMD(usageDeleteMarkersCount,
		"Total cluster delete markers count")
	usageBucketsCountMD = NewGaugeMD(usageBucketsCount,
		"Total cluster buckets count")
	usageObjectsDistributionMD = NewGaugeMD(usageSizeDistribution,

containing the secretKey - `users[].policy` - name of the policy to assign to user ## Uninstalling the Chart Assuming your release is named as `my-release`, delete it using the command: ```bash helm delete my-release ``` or ```bash helm uninstall my-release ``` The command removes all the Kubernetes components associated with the chart and deletes the release....

containing the secretKey - `users[].policy` - name of the policy to assign to user ## Uninstalling the Chart Assuming your release is named as `my-release`, delete it using the command: ```bash helm delete my-release ``` or ```bash helm uninstall my-release ``` The command removes all the Kubernetes components associated with the chart and deletes the release....

containing the secretKey - `users[].policy` - name of the policy to assign to user ## Uninstalling the Chart Assuming your release is named as `my-release`, delete it using the command: ```bash helm delete my-release ``` or ```bash helm uninstall my-release ``` The command removes all the Kubernetes components associated with the chart and deletes the release....

// things like the available devices, resource manager etc.
// TFE_Context must outlive all tensor handles created using it. In other
// words, TFE_DeleteContext() must be called after all tensor handles have
// been deleted (with TFE_DeleteTensorHandle).
//
// TODO(ashankar): Merge with TF_Session?
typedef struct TFE_Context TFE_Context;

TF_CAPI_EXPORT extern TFE_Context* TFE_NewContext(

containing the secretKey - `users[].policy` - name of the policy to assign to user ## Uninstalling the Chart Assuming your release is named as `my-release`, delete it using the command: ```bash helm delete my-release ``` or ```bash helm uninstall my-release ``` The command removes all the Kubernetes components associated with the chart and deletes the release....

        }
    ]
}
```

### 3.3 Automatic removal of delete markers with no other versions

When an object has only one version as a delete marker, the latter can be automatically removed after a certain number of days using the following configuration:

```
{
    "Rules": [
        {
            "ID": "Removing all delete markers",
            "Expiration": {

                        getLogger().debug(metadata + " could not be found on repository: " + repository.getId());

                        // delete the local copy so the old details aren't used.
                        if (file.exists()) {
                            if (!file.delete()) {
                                // sleep for 10ms just in case this is windows holding a file lock
                                try {