entity.asDocMeta().indexOption(opLambda);
        doInsertOrUpdate(entity, null, null);
    }

    public void delete(DataConfig entity) {
        doDelete(entity, null);
    }

    public void delete(DataConfig entity, RequestOptionCall<DeleteRequestBuilder> opLambda) {
        entity.asDocMeta().deleteOption(opLambda);
        doDelete(entity, null);
    }

        entity.asDocMeta().indexOption(opLambda);
        doInsertOrUpdate(entity, null, null);
    }

    public void delete(LabelType entity) {
        doDelete(entity, null);
    }

    public void delete(LabelType entity, RequestOptionCall<DeleteRequestBuilder> opLambda) {
        entity.asDocMeta().deleteOption(opLambda);
        doDelete(entity, null);
    }

> Without a 'Complete' status any 'Active' or 'Draining' pool(s) are not allowed to be removed once configured.

## NOTE

- Empty delete markers (such as for objects with no other successor versions) do not transition to the new pool to avoid creating empty metadata on the other pool(s). If you believe transitioning empty delete markers is required, open a GitHub issue.

## TODO

 * keyword depends on the language and sometimes the context in which a keyword is used. For example,
 * `delete` is an operator in JavaScript, but it isn't in the keywords list for JavaScript or
 * TypeScript because it's OK to use `delete` as a method name.
 */
public class ValidateJsonNoKeywordsTask extends DefaultTask {

        entity.asDocMeta().indexOption(opLambda);
        doInsertOrUpdate(entity, null, null);
    }

    public void delete(FileConfig entity) {
        doDelete(entity, null);
    }

    public void delete(FileConfig entity, RequestOptionCall<DeleteRequestBuilder> opLambda) {
        entity.asDocMeta().deleteOption(opLambda);
        doDelete(entity, null);
    }

        entity.asDocMeta().indexOption(opLambda);
        doInsertOrUpdate(entity, null, null);
    }

    public void delete(SearchLog entity) {
        doDelete(entity, null);
    }

    public void delete(SearchLog entity, RequestOptionCall<DeleteRequestBuilder> opLambda) {
        entity.asDocMeta().deleteOption(opLambda);
        doDelete(entity, null);
    }

    /**
     * Permission to delete a file or directory
     */
    int FILE_DELETE = 0x00000040; // 7
    /**
     * Permission to read file attributes
     */
    int FILE_READ_ATTRIBUTES = 0x00000080; // 8
    /**
     * Permission to write file attributes
     */
    int FILE_WRITE_ATTRIBUTES = 0x00000100; // 9
    /**
     * Standard delete permission
     */
    int DELETE = 0x00010000; // 16

        });
        return redirect(getClass());
    }

    /**
     * Delete a bad word.
     * @param form The edit form.
     * @return The HTML response.
     */
    @Execute
    @Secured({ ROLE })
    public HtmlResponse delete(final EditForm form) {
        verifyCrudMode(form.crudMode, CrudMode.DETAILS, this::asListHtml);

    /**
     * Permission to delete the file.
     */
    int FILE_DELETE = 0x00000040; // 7
    /**
     * Permission to read file attributes.
     */
    int FILE_READ_ATTRIBUTES = 0x00000080; // 8
    /**
     * Permission to write file attributes.
     */
    int FILE_WRITE_ATTRIBUTES = 0x00000100; // 9
    /**
     * Permission to delete the object.
     */

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....