*/
    public void delete(final DuplicateHost duplicateHost) {

        duplicateHostBhv.delete(duplicateHost, op -> {
            op.setRefreshPolicy(Constants.TRUE);
        });

    }

    /**
     * Retrieves all duplicate host configurations without pagination.
     *

    }

    /**
     * Deletes all suggest words from the system.
     *
     * @return JSON response indicating success or failure
     */
    // DELETE /api/admin/suggest/all
    @Execute
    public JsonResponse<ApiResult> delete$all() {
        if (!suggestHelper.deleteAllWords()) {

            op.setRefreshPolicy(Constants.TRUE);
        });

    }

    /**
     * Deletes a failure URL entity from the data store.
     *
     * @param failureUrl the FailureUrl entity to delete
     */
    public void delete(final FailureUrl failureUrl) {

        failureUrlBhv.delete(failureUrl, op -> {
            op.setRefreshPolicy(Constants.TRUE);
        });

    }

    /**

     */
    public void delete(final DataConfig dataConfig) {
        dataConfigBhv.delete(dataConfig, op -> {
            op.setRefreshPolicy(Constants.TRUE);
        });
    }

    /**
     * Retrieves a data configuration by its unique identifier.
     *
     * @param id the unique identifier of the data configuration

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

            op.setRefreshPolicy(Constants.TRUE);
        });

    }

    /**
     * Deletes a role.
     * @param role The role to delete.
     */
    public void delete(final Role role) {
        ComponentUtil.getLdapManager().delete(role);

        roleBhv.delete(role, op -> {
            op.setRefreshPolicy(Constants.TRUE);
        });

        });

    }

    /**
     * Deletes a group from both LDAP and the database, and removes the group
     * association from all users that belong to this group.
     *
     * @param group the group entity to delete
     */
    public void delete(final Group group) {
        ComponentUtil.getLdapManager().delete(group);

        groupBhv.delete(group, op -> {
            op.setRefreshPolicy(Constants.TRUE);

    }

    /**
     * Deletes a related content entity from the database.
     * After deletion, updates the related content helper to refresh the cache.
     *
     * @param relatedContent the RelatedContent entity to delete
     */
    public void delete(final RelatedContent relatedContent) {

        relatedContentBhv.delete(relatedContent, op -> op.setRefreshPolicy(Constants.TRUE));

        return fileConfigList;
    }

    /**
     * Deletes a file configuration and its associated authentication records.
     * This method removes the file configuration from the database and also
     * deletes all related file authentication entries.
     *
     * @param fileConfig the file configuration to be deleted
     */
    public void delete(final FileConfig fileConfig) {

    }

    /**
     * Deletes a user setting by ID.
     *
     * @param id the ID of the user setting to delete
     * @return JSON response indicating success or failure
     */
    // DELETE /api/admin/user/setting/{id}
    @Execute
    public JsonResponse<ApiResult> delete$setting(final String id) {
        final User entity = userService.getUser(id).orElseGet(() -> {