AccountGroupings Object

When Truto actually read this object from the provider, in UTC ISO 8601 with the offset present. Not when the request was made and not a provider timestamp. Drives consumer staleness rules.

The provider's own identifier for the grouping node.

What kind of node this is. On AWS no field carries this: it is derived from the identifier prefix and from which operation returned the node, and is flagged as derived.

Truto's stable unified identifier for this object. Opaque; use provider_ref to address the object in the provider's own console or API.

The grouping name.

The provider's own type string, unmodified -- for example 'AWS::S3::Bucket', 'aws_iam_role', 'Microsoft.Sql/servers'. Used for display and drill-down.

Which cloud this object was read from.

The provider's own unbroken identifier, passed through verbatim -- a full ARN, resource id or self-link. Never truncated, prefixed or normalised. This is the customer-facing key used to find the object in the console.

Accounts directly beneath this node. An empty array means the node genuinely holds no accounts; a node whose children could not be read leaves this null with an unreadable_fields entry.

Grouping nodes directly beneath this one.

Whether grouping_type was read from the provider or derived.

The organisation, tenant or GCP organisation this node belongs to.

The node directly above this one. Null for the organisation root.

Full path from the organisation root to this node. On AWS an organisation root carries no path field and one is synthesized from the organisation and root identifiers.

Where the object is. A compliance answer in its own right, not metadata. The literal string 'global' is emitted for genuinely global resources (for example IAM, or a GCP VPC network) rather than guessing a region. Never invented: where the provider does not return a location and none can be derived, the collector's queried region is used and that substitution is recorded in unreadable_fields.

Raw data returned from the remote API call.

Key-value pairs exactly as the customer set them: no case folding, no key or value normalisation, no merging of separate provider concepts. Present on every object because tags are the primary input for environment classification. An empty object means the object carries no tags; tags that could not be read are recorded in unreadable_fields instead.

Per-object list of the fields that could not be read, and why -- the brief section 8.4 answer, chosen over per-field sentinel values. Each entry is an object with 'field' (the property name on this resource), 'reason' (a reason code) and an optional human-readable 'detail'. Reason codes: not_supported_by_provider, not_configured, permission_denied, not_collected, collection_error, partially_collected. An empty array means every property on this object was read successfully. A property absent from this array and null in the payload means the provider genuinely returned no value, which is different from 'we could not look'.