Resources

Git-Managed Resources

Open Platform as Code → Resources for a read-only inventory of platform objects discovered from Git manifests and reconciled by Axio. To change a resource, edit its YAML in the source repository, commit, push, and synchronize — not from this screen.

Info

Prerequisites

A Git repository connected under Administration → Integrations → Source Control, registered for Platform as Code, with at least one successful synchronization from Platform as Code → Synchronizations. Viewing requires pac:read or higher.

Warning

Important

This page is an observability and inventory view — not an editor. Git-managed resources show a Git-managed indicator in Organization views; manual UI edits to those resources are restricted. When drift is detected, you can reconcile from Git via Sync now or open a pull request to align Git with the platform (Administrators).

1

Browse the inventory

Review the table of Platform as Code resources — name, kind (type), repository, branch, manifest path, commit, sync status, drift, and last sync time. Use pagination to move through large lists.

2

Open resource details

Click a row to open the detail dialog. Review sync status chips, repository, manifest path, applied commit, and the read-only manifest YAML (sourceYaml).

3

Review Git source

Confirm which repository, branch, manifest file path, and commit SHA last applied the resource. The manifest path is relative to the repository working directory (for example platform-config/environments/production.yaml).

4

Check sync status

Inspect Sync Status — for example READY, PENDING, FAILED, DRIFTED, or AWAITING APPROVAL when a sync plan includes the resource and requires approval.

5

Monitor drift and dependencies

The Drift column shows In sync or Drifted when live platform state differs from Git. Pending resources may list blocked dependencies (for example a Workspace that must reconcile before an Environment).

6

Act on drift or approval

For drift, go to Synchronizations and Sync now to reconcile from Git, or use Open PR to fix drift (Administrators) to update the manifest to match the platform. Approve or reject pending sync plans from the detail dialog or Operations → Approvals.

Resources

What are Resources?

Resources are Platform as Code objects tracked by Axio after manifest discovery and reconciliation. Each row represents a kind and name (for example Environment/production), its synchronization state, drift relative to Git, and the repository commit that last applied it. Resources with a linked repository are Git-managed; others may appear with Git Managed: No until synchronized from a repo.

Columns

Inventory columns

  • Name — Resource name (metadata.name)
  • Type — Resource kind (Project, Workspace, Environment, …)
  • Git Managed — Whether the resource is tied to a synchronized repository
  • Repository / Branch — Source repo and branch
  • Manifest Path — File path within the working directory
  • Commit — Short SHA of the last applied commit
  • Sync Status — Reconciliation phase (see statuses below)
  • Drift — In sync or Drifted vs Git definition
  • Last Sync — Timestamp of last reconciliation
Tip

Tip

Resources reflect state as reported by Axio after the last sync run. Use Synchronizations → Sync now to reconcile Git with the platform, or History for a read-only audit of past runs.

Common sync statuses:

  • READY – Reconciled and available in the platform
  • PENDING – Waiting to apply (often blocked on a parent dependency)
  • AWAITING APPROVAL – Included in a sync plan that requires approval
  • Drifted – Live platform state differs from the Git manifest (see Drift column)
  • FAILED – Reconciliation or validation failed (check Synchronizations / History)
  • UNKNOWN – Status not yet determined

Browse kind schemas in Catalog before authoring new manifests.