Bulk unassign devices from a group

After the device is removed from its group, this option initiates a job to factory reset the specified Redfish subsystem(s). This option is only valid for servers and "BIOS" is the only supported subsystem.

filter

string

Limit the resources operated on by an endpoint or when used with a multiple-GET endpoint, return only the subset of resources that match the filter. The filter grammar is a subset of OData 4.0.

NOTE: The filter query parameter must use URL encoding. Most clients do this automatically with inputs provided to them specifically as query parameters. Encoding must be done manually for any query parameters provided as part of the URL.
The reserved characters ! # $ & ' ( ) * + , / : ; = ? @ [ ] must be encoded with percent encoded equivalents. Server IDs contain a +, which must be encoded as %2B.
For example: the value P06760-B21+2M212504P8 must be encoded as P06760-B21%2B2M212504P8 when it is used in a query parameter.

CLASS	EXAMPLES
Types	integer, decimal, timestamp, string, boolean, null
Operations	eq, ne, gt, ge, lt, le, in
Logic	and, or, not

Groups can be filtered by:

autoAddServerTags
autoFwUpdateOnAdd
createdAt
description
generation
groupComplianceStatus
id
name
platformFamily
serverPolicies
serverSettingsUris
updatedAt

The following examples are not an exhaustive list of all possible filtering options.

Examples:

Filter with equality check

Return groups where a property equals a value. <property> eq <value>

filter=name eq 'Production Group'

Filter with equality check on a nested attribute

Return groups where a nested property equals a value. <property>/<nestedProperty> eq <value>

filter=autoAddServerTags/Department eq 'Development - Texas'

Filter with url encoding applied to all reserved characters (example is fully URL encoded)

Return group where name == my+group

filter=name%20eq%20%27my%2Bgroup%27

Filter on an inverted query

Return groups where a property does not equal a value not <property> eq <value>

filter=not autoAddServerTags/Department eq 'Development - Texas'

Filter that a property contains a value

Return groups with populated property. not <property> eq null

filter=not name eq null

Filter that field value contains a specific substring

Return groups where property contains a value. contains(<property>, <value>)

filter=contains(name,'Group')

Filter on multiple conditionals

Return groups where property is populated and property contains value. not <property> eq null and contains(<property>, <value>)

filter=not name eq null and contains(name,'Group')

Filter for a value to have one of multiple possibilities

Return groups where property is one of multiple values. <property>/<nestedProperty> in (<value>,<value>)

filter=autoAddServerTags/Department in ('Development - Texas','Development - Colorado')

header Parameters

Tenant-Acid

string <uuid>

Tenant-Acid header can be used by an MSP workspace to make API calls on behalf of their tenant by specifying the tenant's application customer ID.

In order to make such an API call, the Bearer token must belong to an MSP workspace and this header value must be the application customer ID of a tenant within the MSP workspace. Use the /compute-ops-mgmt/v1beta1/accounts API to determine the application customer IDs for your tenant accounts.

Responses

204

Successful Response

400

Bad request

401

Unauthorized

403

Forbidden

404

Not found

406

Not acceptable

500

Internal server error

Request samples

curl
JavaScript
Python
Go

Response samples

application/json

{"httpStatusCode": 400,
"errorCode": "HPE-GL-COMPUTE_OPS-0500001",
"message": "string",
"debugId": "string",
"errorDetails": [{"type": "hpe.greenlake.bad_request",
"issues": [{"source": "field",
"subject": "user.phone",
"description": "string"
}
]
}
]
}