io.github.HewlettPackard/greenlake-audit-logs-mcp

Executes any workspaces API endpoint dynamically with parameter validation. Args: ctx: FastMCP context providing access to the shared HTTP client. endpoint_identifier: Endpoint identifier in METHOD:PATH format. parameters: Optional dict of path and/or query parameters. validate_schema: Whether to validate parameters against the OpenAPI schema. Returns: A list containing one result dict with the API response or an error message.

Retrieves detailed schema information for a specific workspaces API endpoint. Args: endpoint_identifier: Endpoint identifier in METHOD:PATH format. include_examples: Whether to include example parameter values. Returns: A list containing one result dict with the endpoint schema or an error message.

Retrieve detailed workspace information. Args: workspaceId: The unique identifier of the workspace. Example: 7600415a-8876-5722-9f3c-b0fd11112283 Returns: API response data as a list containing one result dict.

Lists all available workspaces API endpoints with metadata for fast discovery. Returns a JSON-encoded array of endpoint objects with 'endpoint' (METHOD:PATH), 'summary' (operation name), and 'type' ('list' for collection endpoints, 'detail' for single-resource endpoints requiring path parameters). Args: filter: Optional case-insensitive substring filter applied to endpoint identifiers and summaries. Returns: JSON string containing a sorted list of endpoint objects.

Retrieve basic workspace information for a provided workspace identifier. Args: workspaceId: The unique identifier of the workspace. Example: 7600415a-8876-5722-9f3c-b0fd11112283 Returns: API response data as a list containing one result dict.

This API is designed to fetch the status of all reports for a specific workspace. Only reports belonging to the workspace ID and username are returned. This API supports pagination, allowing you to use offset and limit parameters. Args: filter: Example: type eq "REPORT" **Filter Syntax**: Use OData-style filters with the field names shown in the examples above. String values must be enclosed in double quotes. sort: The order in which to return the resources in the collection.The value of the sort query parameter is a comma separated list of sort expressions. Each sort expression is a property name optionally followed by a direction indicator asc (ascending) or desc (descending).The first sort expression in the list defines the primary sort order, the second defines the secondary sort order, and so on. If a direction indicator is omitted the default direction is ascending. Examples: - name asc Order ascending by name - name,createdAt desc Order resources ascending by name and then by descending by createdAt limit: The maximum number of reports to return. Example: 50 offset: Zero-based resource offset to start the response from. Example: 20 Returns: API response data as a list containing one result dict.

Retrieve the status of a specific report by passing the report status ID. Args: id: The report status identifier. Example: 3fa85f64-5717-4562-b3fc-2c963f66afa6 Returns: API response data as a list containing one result dict.

Get subscriptions managed in a workspace. Filters can be passed to filter the subscriptions based on conditional expressions.<br><br>**NOTE:** You need to have view permission for the **Devices and subscription service** to invoke this API. <br><br> Rate limits are enforced on this API. 60 requests per minute is supported per workspace. API will result in `429` if this threshold is breached. Args: filter: Filter expressions consisting of simple comparison operations joined by logical operators.<br> | CLASS | EXAMPLES | |----------------------|----------------------------------------------------| | Types | integer, decimal, timestamp, string, boolean, null | | Comparison | eq, ne, gt, ge, lt, le, in | | Logical Expressions | and, or, not | Subscriptions can be filtered based on the following properties: - `id` - `subscriptionType` - `subscriptionStatus` - `key` - `quantity` - `availableQuantity` - `sku` - `skuDescription` - `contract` - `startTime` - `endTime` - `productType` - `tier` - `tierDescription` - `quote` - `po` - `resellerPo` - `createdAt` - `updatedAt` The following is a non-exhaustive list of possible filtering options. Examples: - subscriptionType in 'CENTRAL_STORAGE', 'CENTRAL_CONTROLLER' Return subscriptions where the property is one of multiple values. Example syntax, \<property> in \<value>,\<value>. - key eq 'STIQQ4L04' and subscriptionType eq 'CENTRAL_STORAGE' The AND operator returns results that meet all filter queries. In the example, the query only returns subscriptions with the exact key and with the specified subscription type. Example syntax, \<property> eq \<value> and \<property> eq \<value>. - key eq 'STIQQ4L04' or subscriptionType eq 'CENTRAL_STORAGE' The OR operator returns results that meet any of the filter queries. In the example, the query returns subscriptions with the exact key or with the specified subscription type. - key eq 'STIAPL6404' Return subscriptions where a property equals a value. Example syntax, \<property> eq \<value>. - createdAt ge '2024-01-18T19:53:51.480Z' Return subscriptions where a property is greater or equal to a value. Example syntax, \<property> ge \<value>. - updatedAt le '2024-02-18T19:53:51.480Z' Return subscriptions where a property is less than or equal to a value. Example syntax, \<property> le \<value>. - startTime gt '2024-01-23T00:00:00.000Z' and endTime lt '2025-02-22T00:00:00.000Z' and not productType eq 'SERVICE' The AND, OR, and NOT operators can be combined to return results that satisfy all specified filter criteria. - tier ne 'BRIDGE' Return subscriptions where a property does not equate to a value. Example syntax, \<property> ne \<value>. - not key eq 'STIAPL6404' Return subscriptions where a property does not equal a value. Example syntax, not \<property> eq \<value>. **Filter Syntax**: Use OData-style filters with the field names shown in the examples above. String values must be enclosed in single quotes. **Field Type Hints**: Quote string and date-time values. Use unquoted literals for integer, number, and boolean fields unless the examples above show a different syntax. - `id`: string - `subscriptionType`: string - `subscriptionStatus`: string - `key`: string - `quantity`: string - `availableQuantity`: string - `sku`: string - `skuDescription`: string - `contract`: string - `startTime`: string - `endTime`: string - `productType`: string - `tier`: string - `tierDescription`: string - `quote`: string - `po`: string - `resellerPo`: string - `createdAt`: string - `updatedAt`: string filter-tags: Filter expressions consisting of simple comparison operations joined by logical operators to be applied on the assigned tags or their values.<br> | CLASS | EXAMPLES | |---------------------|-----------------| | Types | string | | Comparison | eq, ne | | Logical Expressions | and, or | Examples: - 'city' eq 'London' and 'street' eq 'Piccadilly' Return subscriptions containing the tag key and the corresponding value that satisfy all conditionals. Example syntax, \<property> eq \<value> and \<property> eq \<value>. - 'street' eq 'Oxford Street' or 'street' eq 'Piccadilly' Return subscriptions containing the tag key and the corresponding value that satisfy at least one of the conditionals. Example syntax, \<property> eq \<value> or \<property> eq \<value>. - 'city' eq 'London' Return subscriptions that have a pair of tags with the exact same tag key and tag value. Example syntax, \<tagKey> eq \<tagValue>. - 'city' ne 'London' Return subscriptions that have a pair of tags with the exact same tag key and the exact different tag value. Example syntax, \<tagKey> ne \<tagValue>. **Filter Syntax**: Use OData-style filters with the field names shown in the examples above. String values must be enclosed in single quotes. sort: A comma separated list of sort expressions. A sort expression is a property name optionally followed by a direction indicator `asc` or `desc`. The default is ascending order. Example: key, quote desc select: A comma separated list of select properties to display in the response. The default is that all properties are returned. Example: id,key **Selectable properties**: `availableQuantity`, `contract`, `createdAt`, `endTime`, `id`, `isEval`, `key`, `po`, `productType`, `quantity`, `quote`, `resellerPo`, `sku`, `skuDescription`, `startTime`, `subscriptionStatus`, `subscriptionType`, `tags`, `tier`, `tierDescription`, `type`, `updatedAt`. Use only these exact property names in `select`; unsupported properties can return HTTP 400 errors. limit: Specifies the number of results to be returned. The default value is 50. offset: Specifies the zero-based resource offset to start the response from. The default value is 0. Returns: API response data as a list containing one result dict.

Get detailed information for a single subscription by `id`. <br><br>**NOTE:** You need to have the view permission of device management to invoke this API. <br><br> Rate limits are enforced on this API. 20 requests per minute is supported per workspace. The API returns `429` if this threshold is breached. Args: id: The unique identifier of the subscription. Returns: API response data as a list containing one result dict.

Get details on a specific device by passing its resourceId. <p><b>NOTE</b>: You need view permissions for device management to invoke this API.</p> Rate limits are enforced on this API. 40 requests per minute is supported per workspace. The API returns `429` if this threshold is breached. Args: id: id parameter Returns: API response data as a list containing one result dict.

With this API, you can: <ul><li>Retrieve a list of devices managed in a workspace.</li> <li>Filter devices based on conditional expressions.</li></ul><p><b>NOTE</b>: You need view permissions for Devices and Subscription service to invoke this API.</p> Rate limits are enforced on this API. 160 requests per minute is supported per workspace. The API returns `429` if this threshold is breached. Args: filter: Filter expressions consisting of simple comparison operations joined by logical operators.<br> | CLASS | EXAMPLES | |---------------------|----------------------------------------------------| | Types | integer, decimal, timestamp, string, boolean, null | | Comparison | eq, ne, gt, ge, lt, le, in | | Logical Expressions | and, or, not | The following examples are not an exhaustive list of all possible filtering options. Examples: - deviceType in 'COMPUTE', 'STORAGE' Return devices where a property is one of multiple values. Example syntax, \<property> in \<value>,\<value>. - deviceType eq 'STORAGE' and partNumber eq 'RTICXL6413' Return devices that exactly satisfy multiple filter queries. Example syntax, \<property> eq \<value> and \<property> eq \<value>. - serialNumber eq 'STIAPL6404' or partNumber eq 'RTICXL6413' Return devices that exactly satisfy one of multiple filter queries. Example syntax, \<property> eq \<value> or \<property> eq \<value>. - serialNumber eq 'STIAPL6404' Return devices where a property equals a value. Example syntax, \<property> eq \<value>. - createdAt ge ''2024-01-18T19:53:51.480Z'' Return devices where a property is greater or equal to a value. Example syntax, \<property> ge \<value>. - updatedAt le '2024-02-18T19:53:51.480Z' Return devices where a property is lesser or equal to a value. Example syntax, \<property> ge \<value>. - not serialNumber eq 'STIAPL6404' Return devices where a property does not equal a value. Example syntax, not \<property> eq \<value>. **Filter Syntax**: Use OData-style filters with the field names shown in the examples above. String values must be enclosed in single quotes. filter-tags: Filter expressions consisting of simple comparison operations joined by logical operators to be applied on the assigned tags or their values.<br> | CLASS | EXAMPLES | |---------------------|-----------------| | Types | string | | Comparison | eq, ne, in | | Logical Expressions | and, or, not | Examples: - 'street' in 'Regent Street', 'Oxford Street', 'Piccadilly' Return devices containing the tag key and at least one of the specified values. Example syntax, \<property> in \<value>,\<value>. - 'city' eq 'London' and 'street' eq 'Piccadilly' Return devices that exactly satisfy multiple filter queries applied to tag keys. Example syntax, \<property> eq \<value> and \<property> eq \<value>. - 'street' eq 'Oxford Street' or 'street' eq 'Piccadilly' Return devices that satisfy any of multiple filter queries applied to tag keys. Example syntax, \<property> eq \<value> or \<property> eq \<value>. - 'city' eq 'London' Return devices where a tag key is equal to a tag value. Example syntax, \<tagKey> eq \<tagValue>. - not 'city' eq 'Tokyo' Return devices where a tag key does not equal a tag value. Example syntax, not \<property> eq \<value>. **Filter Syntax**: Use OData-style filters with the field names shown in the examples above. String values must be enclosed in single quotes. sort: A comma separated list of sort expressions. A sort expression is a property name optionally followed by a direction indicator `asc` or `desc`. The default is ascending order. Example: serialNumber,macAddress desc select: A comma separated list of select properties to display in the response. The default is that all properties are returned. Example: serialNumber,macAddress **Selectable properties**: `application`, `archived`, `assignedState`, `createdAt`, `dedicatedPlatformWorkspace`, `deviceName`, `deviceType`, `id`, `location`, `macAddress`, `model`, `partNumber`, `region`, `secondaryName`, `serialNumber`, `subscription`, `tags`, `tenantWorkspaceId`, `type`, `updatedAt`, `warranty`. Use only these exact property names in `select`; unsupported properties can return HTTP 400 errors. limit: Specifies the number of results to be returned. The default value is 2000. offset: Specifies the zero-based resource offset to start the response from. The default value is 0. Returns: API response data as a list containing one result dict.

The audit logs can be filtered using a variety of parameters. Queries should be separated by `and` and can utilize `eq`, `contains`, and `in` operators to construct the final query. Each query should follow the format: * key eq 'value' for equality operation. * contains(key, 'value') for contains operation. * key in ('value1', 'value2') for in operation. | Filter parameter | Supported Operators | Type | Example | |--------------------------|---------------------|-------------------------|-------------------------------------------------------------------------------------------------| | createdAt | lt, ge | RFC timestamp in string | createdAt ge '2024-02-16T07:54:55.0Z' | | category | eq, in | string | category eq 'User Management' category in ('Device Management', 'User Activity') | | description | eq, contains | string | contains(description, 'Logged in') description eq 'User test@test.com logged in via ping mode.' | | additionalInfo/ipAddress | eq, contains | IP string | additionalInfo/ipAddress eq '192.168.12.12' contains(additionalInfo/ipAddress, '192.168') | | user/username | eq, contains | email in string | user/username eq 'test@test.com' contains(user/username, '@gmail.com') | | workspace/workspaceName | eq, contains | string | workspace/workspaceName eq 'Example workspace' contains(workspace/workspaceName, 'Example') | | application/id | eq | UUID in string | application/id eq '12312-123123-123123-123121' | | region | eq | region code in string | region eq 'us-west' | | hasDetails | eq | boolean | hasDetails eq 'true' | Args: filter: Example: category eq 'User Management' and contains(description, 'logged out') **Filter Syntax**: Use OData-style filters with the field names shown in the examples above. String values must be enclosed in single quotes. select: Use the `select` query parameter to restrict the number of properties included in the audit log response. The supported select parameters: * additionalInfo * createdAt * category * hasDetails * workspace/workspaceName * description * user/username Example: createdAt, user/username, category **Selectable properties**: `additionalInfo`, `createdAt`, `category`, `hasDetails`, `workspace/workspaceName`, `description`, `user/username`. Use only these exact property names in `select`; unsupported properties can return HTTP 400 errors. all: Provide a free-text search to perform a comprehensive search across all properties for audit logs. Example: logged in user limit: How many items to return at one time (max 2000) offset: Specifies the zero-based resource offset to start the response from. Returns: API response data as a list containing one result dict.

Get additional detail of an audit log. Args: id: Provide the ID of the audit log record that has the `hasDetails` value set to `true` to fetch the additional details. Returns: API response data as a list containing one result dict.

Retrieve a single user based on a given user ID. Args: id: The unique identifier of the user. Example: 7600415a-8876-5722-9f3c-b0fd11112283 Returns: API response data as a list containing one result dict.

Retrieve list of users with filtering, and pagination options. All users are returned when no filters are provided. **Note**: User view all permission is required to invoke this API. Rate limit: 300 requests per minute per workspace, resulting in a `429` error if exceeded. Args: filter: Filter data using a subset of OData 4.0 and return only the subset of resources that match the filter. Supported classes and examples include: - **Types**: timestamp, string - **Comparison**: eq, ne, gt, ge, lt - **Logical Expressions**: and, or, not The Get users API can be filtered by: - id - username - userStatus - createdAt - updatedAt - lastLogin userStatus can be one of the following: - UNVERIFIED - VERIFIED - BLOCKED - DELETE_IN_PROGRESS - DELETED - SUSPENDED **Note**: The userStatus filter is case-sensitive. Examples: - createdAt gt '2020-09-21T14:19:09.769747' Returns users created after 2020-09-21T14:19:09.769747 - username eq 'user@example.com' Returns the user with a specific email. - id eq '7600415a-8876-5722-9f3c-b0fd11112283' Returns the user with a specific ID. - lastLogin lt '2020-09-21T14:19:09.769747' Returns users that logged in before 2020-09-21T14:19:09.769747 - updatedAt gt '2020-09-21T14:19:09.769747' Returns users updated after 2020-09-21T14:19:09.769747 - userStatus ne 'UNVERIFIED' Returns users that are not unverified. - username eq 'user@example.com' Returns the user with a specific username. **Filter Syntax**: Use OData-style filters with the field names shown in the examples above. String values must be enclosed in single quotes. **Field Type Hints**: Quote string and date-time values. Use unquoted literals for integer, number, and boolean fields unless the examples above show a different syntax. - `id`: string (uuid) - `username`: string (email) - `userStatus`: string - `createdAt`: string (date-time) - `updatedAt`: string (date-time) - `lastLogin`: string (date-time) offset: Specify pagination offset. An offset argument defines how many pages to skip before returning results. limit: Specify the maximum number of entries per page. NOTE: The maximum value accepted is 600. Returns: API response data as a list containing one result dict.

Retrieve detailed information about a specific service offer region by providing its unique identifier in the request path. To obtain valid service offer region IDs, use the `Get service offer regions` endpoint to list available regions. Args: id: The unique service offer region ID. Example: 3fa85f64-5717-4562-b3fc-2c963f66afa6 Returns: API response data as a list containing one result dict.

Fetch service provision details for an ID. Args: id: The unique identifier of a service provision. The ID is returned by the `Get service provisions` endpoint. unredacted: If set to true, get the entire entry along with sensitive fields. Example: true Returns: API response data as a list containing one result dict.

Retrieve detailed information about a specific service offer by supplying its unique identifier in the request path. To obtain valid service offer IDs, use the `Get service offers` endpoint to list available offers. Args: id: The unique identifier of the service offer. Example: 3fa85f64-5717-4562-b3fc-2c963f66afa6 Returns: API response data as a list containing one result dict.

Retrieve a list of all service manager provision entries. Args: offset: Zero-based resource offset to start the response from. Example: 0 limit: The maximum number of records to return. Example: 10 filter: Examples: - serviceManagerId eq '767c0c92-5ecc-4952-85d6-06d2bcaaf050' Returns service managers with a specific service manager ID. - status eq 'PROVISIONED' Returns service managers that are provisioned. - status eq 'UNPROVISIONED' Returns service managers that are not provisioned. - region eq 'us-west' Returns service managers in a specified region. **Filter Syntax**: Use OData-style filters with the field names shown in the examples above. String values must be enclosed in single quotes. Returns: API response data as a list containing one result dict.

Retrieve a list of service provisions by applying filters. A service offer provides a distinct set of functionalities that can be independently identified and assigned access. Service offers are typically associated with roles and permissions, commerce, metering, quote-to-cash, and trial evaluations. A service provision occurs when a service offer is provisioned (added) to a workspace. <br><br>**Pagination**: This endpoint supports cursor-based pagination using the `next` query parameter. Provide the cursor in the `next` query parameter to retrieve the next page. Args: Hpe-workspace-id: The workspace ID. Required if the "view all" parameter is false. next: Specify the start ID for the next page of service offers. limit: Specify the number of results to be returned. filter: Limit the entities operated on by this endpoint by returning only the subset of entities that match the filter. The filter grammar is a subset of OData 4.0. <br> **Supported Fields:** `id`, `ServiceOfferId`, `workspaceId`, `serviceManagerProvisionId`, `serviceManagerId`, `serviceManagerInstanceId`, `status`, `organizationId`, `slug`. <br> **Supported operand:** `eq` <br> **Supported operations:** `and` Examples: - id eq '767c0c92-5ecc-4952-85d6-06d2bcaaf050' Return the service provision with a given ID. - workspaceId eq '767c0c92-5ecc-4952-85d6-06d2bcaaf050' Return service provisions for a given workspace ID. - serviceManagerProvisionId eq '767c0c92-5ecc-4952-85d6-06d2bcaaf050' Return service provisions for a given Application Customer ID. - ServiceOfferId eq '767c0c92-5ecc-4952-85d6-06d2bcaaf050' and region eq 'us-west' Return service provisions for a given service offer ID and region. - serviceManagerId eq '767c0c92-5ecc-4952-85d6-06d2bcaaf050' and serviceManagerInstanceId eq '62d242c7-7d53-448d-b7d0-baf0c591f024' Return service provision for a given application ID and application instance ID. - status eq 'PROVISION_INITIATED' Return service provisions with a given status. - organizationId eq '767c0c92-5ecc-4952-85d6-06d2bcaaf050' Return service provisions with a given organization ID. - slug eq 'AC' Return service provisions with a given slug. **Filter Syntax**: Use OData-style filters with the field names shown in the examples above. String values must be enclosed in single quotes. unredacted: If true, returns the complete entry including sensitive fields. Example: true all: If true, returns unredacted entries for all workspaces, including all provisioned service offers and their sensitive fields. Example: true Returns: API response data as a list containing one result dict.

Retrieve a list of service offers by applying filters. A service offer provides a distinct set of functionality that can be independently identified and assigned access. <br><br>**Pagination:** This API supports cursor-based pagination. Provide the cursor in the `next` query parameter to retrieve the next page. Args: next: Specifies the pagination cursor for the next page of service offers. Example: 64136af7-cd64-4b4e-88a8-150ab51a920d limit: Specifies the number of results to be returned. filter: The `filter` query parameter is used to filter the set of resources returned in a `GET` request. The returned set of resources must match the criteria in the filter query parameter.<br><br> The value of the `filter` query parameter is a subset of [OData 4.0](https://www.odata.org/documentation/) filter expressions consisting of simple comparison operations joined by logical operators.<br><br>**Supported fields**: `category`, `serviceManagerId`, `status`, `isDefault`, `slug`, and `staticLaunchUrl`.<br>**Supported operand**: `eq`<br>**Supported operations**: `and` Examples: - category eq 'COMPUTE' Return service offers for a given category - isDefault eq true Return service offers that are service managers - serviceManagerId eq '767c0c92-5ecc-4952-85d6-06d2bcaaf050' Return service offers for given service manager ID - slug eq 'GLP' Return service offers with a given slug - staticLaunchUrl eq '/Organization' Return service offers for a given static launch URL - status eq 'ONBOARDED' Return service offers with a given status **Filter Syntax**: Use OData-style filters with the field names shown in the examples above. String values must be enclosed in single quotes. Returns: API response data as a list containing one result dict.

Retrieve a list of available service managers categorized by region. Args: offset: Zero-based resource offset to start the response from. Example: 0 limit: The maximum number of records to return. Example: 10 filter: Limit the resources operated on by an endpoint and return only the subset of resources that match the filter using an [OData V4](https://www.odata.org/documentation/) formatted filter string. Service manager by region can be filtered by `mspsupported` See examples of filtering options. Examples: - mspSupported eq true Return service managers when msp supported equals true - mspSupported eq false Return service managers when msp supported equals false **Filter Syntax**: Use OData-style filters with the field names shown in the examples above. String values must be enclosed in single quotes. Returns: API response data as a list containing one result dict.

Get a list of available service managers. Args: offset: Specify pagination offset Example: 0 limit: The maximum number of records to return. Example: 10 Returns: API response data as a list containing one result dict.

Retrieve details for a specific service manager by passing the service manager ID. Args: id: Service manager ID Returns: API response data as a list containing one result dict.

Retrieve details for a specific service manager provision entry using the ID for the entry. Args: id: Service manager provision ID Returns: API response data as a list containing one result dict.

Retrieve a list of service offer regions by applying filters. Each service offer region represents a service offer provisioned in a specific region. <br><br>**Pagination:** This API supports cursor-based pagination. Provide the cursor in the `next` query parameter to retrieve the next page. Args: next: Specifies the pagination cursor for the next page of service offer regions. Example: 64136af7-cd64-4b4e-88a8-150ab51a920d limit: Specifies the number of results to be returned. filter: The `filter` query parameter is used to filter the set of resources returned in a `GET` request. The returned set of resources must match the criteria in the filter query parameter.<br><br> The value of the `filter` query parameter is a subset of [OData 4.0](https://www.odata.org/documentation/) filter expressions consisting of simple comparison operations joined by logical operators.<br><br>**Supported fields**: `serviceOfferId`, `status`, and `region`.<br>**Supported operand**: `eq`<br>**Supported operations**: `and` Examples: - serviceOfferId eq '767c0c92-5ecc-4952-85d6-06d2bcaaf050' and region eq 'us-east' Return service offer regions with a given service offer ID and region - serviceOfferId eq '767c0c92-5ecc-4952-85d6-06d2bcaaf050' and status eq 'ONBOARDED' Return service offer regions with a given service offer ID and status - serviceOfferId eq '767c0c92-5ecc-4952-85d6-06d2bcaaf050' and status eq 'ONBOARDED' and region eq 'us-east' Return service offer regions with a given service offer ID and status and region - region eq 'us-east' Return service offer regions with a given region - status eq 'ONBOARDED' Return service offer regions with a given status - serviceOfferId eq '767c0c92-5ecc-4952-85d6-06d2bcaaf050' Return service offer regions with a given service offer ID **Filter Syntax**: Use OData-style filters with the field names shown in the examples above. String values must be enclosed in single quotes. Returns: API response data as a list containing one result dict.

Retrieve a list of service managers deployed to a particular region. Args: id: HPE GreenLake platform defined region code. Examples: - us-west - us-east Returns: API response data as a list containing one result dict.