Skip to content

Resources

Resources in the sidebar is an inventory of the infrastructure resources Zenfra currently manages across all stacks, indexed from each stack's Terraform state. It answers "what do we run, where, and when did it last change" without opening state files. Every role can view it.

What is indexed

  • Indexing happens after a state commit and is best-effort: it may lag briefly after a stack's first commit, and an empty list does not necessarily mean the stack has no infrastructure.
  • It requires Zenfra-managed state. A stack with customer-managed S3 state shows Resource inventory unsupported for this stack; its runs still get the Resource impact panel, which is derived from plan JSON in both modes.
  • Attribute values are never displayed, because Terraform state can contain sensitive data. Zenfra stores safe fingerprints of attributes for change detection.

The inventory

The list shows each resource's Address, Stack, Provider, Type, Status (Active or Deleted), Signals (Drift, or the number of policy findings), Last changed and Last changed by. Filter by text (address, type or provider), Mode (Managed or Data sources), Status, Provider and Type.

Each stack's Resources tab shows the same view for that stack only.

Resource detail

Opening a resource shows:

  • Metadata: stack, name, mode and index key.
  • Provenance: when it last changed, whether it is deleted, and the run that changed it.
  • Vendor data: the resource's attributes as fingerprints (vendor-data.json), with a count of attributes marked sensitive.
  • Lifecycle: the resource's events (Observed, Created, Updated, Replaced, Deleted, Drift detected, Policy finding), each with the attribute paths that changed.

Drift signals come from drift detection schedules on the stack.