Added platform_info to the response body of the Get a support request endpoint.

The platform_info returns the cloud asset identifier the requester selected on the support form's asset-selector control, typically the GCP project ID, AWS account ID, Azure subscription ID, or equivalent.


Added Cloud Analytics folder API with he following operations:


We are adding support for organizing reports and allocations into folders.

To support this we have added the ability to:

  • Filter reports and allocations by folderId.
  • Add a report or allocation to an existing folder by including folderId in a PATCH request. If folderId is omitted or empty, the item is placed in the root folder.

It is optional to use the folderId. Folders can be created and configured using the Folders API.




Added the following operations and schemas to Cloud Diagrams API:


  • Added an optional email filter to GET /iam/v1/users for direct, stable user lookup by email.

  • Extended POST /iam/v1/users/invite to accept firstName, lastName, and jobTitle.

  • Standardized the user schema on jobTitle across list, update, and invite APIs, deprecating jobFunction.

    For backward compatibility, the API still accepts jobFunction in requests. If a client sends jobFunction instead of jobTitle, the server automatically copies the value into jobTitle and processes it as if jobTitle had been sent. However, we recommend updating your calls to use jobTitle.


Insights API updates to improve Terraform and IaC compatibility and add full resource lifecycle support.

Changes:

  • Added insight operations GET, POST, and DELETE on /insights/v1/results/source/{sourceID}/insight/{insightKey}. You can now read, create/update, and delete one insight by key without relying on bulk-only flows or UI redirects.
  • Replaced unimplemented page / pageSize with pageToken and maxResults on list and resource-results endpoints, to align with other DoiT APIs. Large resource-result sets must be walked with tokens.
  • Changed field provider to cloudProvider.
  • ResourceResults is no longer a discriminated oneOf, each item is a single ResourceResult object with optional fields, using resultType to tell you which fields apply.
  • Money- and score-like numbers are documented and served as double-precision values so automated tools (e.g. Terraform) do not see spurious drift from rounding.

Implementation steps:

  • Update any clients or generated code that uses provider to use cloudProvider.
  • Adopt the flattened ResourceResult model.
  • Switch to cursor pagination.
  • Use the new singular routes where you need stable read/create/delete behavior.

New fields in Anomalies API response schema:

  • acknowledgedAt: When the anomaly was first acknowledged.
  • acknowledgedBy: Email of the user who first acknowledged the anomaly

List requests was ignoring maxResults and pageToken, returning all tickets in a single response.

Changes:

  • pageSize now has a maximum of 100.
  • Default maxResults is updated from 50 to 100.
  • A request of more than 100 results per page returns ErrInvalidMaxResults (400).

Added forecast values to Retrieve a commitment and List commitments API responses:

  • Per-period forecastValue under periods: Returns the projected spend at the period's end date.
  • Top-level total ForecastValue on CommitmentExternal and CommitmentExternalListItem: summary across all periods.
  • When a period has insufficient history for a forecast (empty series), the value is 0.0.