History

GitOps History

Open Platform as Code → History for a read-only audit of every synchronization run — validation, approval, reconciliation, and final outcome. Use Synchronizations for operational tasks such as approving plans, reviewing run details, or cleaning recent run records.

Prerequisites

At least one synchronization must have run (manual, scheduled, or webhook-triggered). Viewers with pac:read can browse history; Administrators and scoped Members use the same read-only view on this tab.

History vs Recent runs

History is a compact audit table across synchronization runs. For plan previews, Approve/Reject actions, duration, change counts, and run cleanup, use Synchronizations → Recent runs. Both views draw from the same sync-run records.

What is History?

GitOps History is an organization-wide audit log of Platform as Code synchronization executions. Each row captures when a run started, which repository and commit were reconciled, how it was triggered, whether validation and approval gates passed, and whether the plan was applied, failed, or rejected.

History columns

Started — Local date and time the run began
Repository — Connected Git repository name
Commit — Short SHA of the reconciled commit
Trigger — Manual (Sync now), scheduled (Auto), or webhook
Validation — Schema and dependency check outcome (valid, invalid, partial)
Approval — Whether a plan required or received approval (pending, approved, not_required, etc.)
Applied — Yes when reconciliation completed successfully
Failed — Yes when validation or apply errors occurred
Rejected — Yes when an approver rejected the plan
Status — Overall run state (completed, failed, awaiting approval, running, rejected)

How History Helps

✓

Audit trail

Maintain a record of Git-driven platform changes for compliance and post-incident review.

⚒

Troubleshooting

Filter failed or rejected runs, then open the same run under Synchronizations → Recent runs for plan details and error messages.

⌁

Trends

Scan validation and approval columns over time to spot recurring schema issues or sensitive-resource approval bottlenecks.

⌑

Traceability

Trace each run back to repository, commit SHA, and trigger type. Commit author and message are included in search even though they are not shown as separate columns.

History at a Glance

▷

Triggered

A run starts from Sync now, an Auto schedule, or a Git webhook.

☷

Discovered & validated

Manifests are fetched from the working directory, parsed, and checked against schemas and policies.

≡

Planned & approved

A sync plan is built; sensitive changes may require approval before apply.

✓

Reconciled

Creates, updates, and staged deletions are applied to platform resources (or the plan is rejected).

▣

Recorded

Outcome, validation, approval, and status appear in GitOps History and Recent runs.

◔

Reviewed

Search and refresh on the History tab, or drill into run details from Synchronizations when action is needed.

Tip

Use the search box to filter by repository, commit SHA, trigger, status, validation, or approval. Click Refresh to reload the latest runs. When a run shows awaiting approval, switch to Synchronizations to Approve or Reject, or open Operations → Approvals for the full request. Administrators can prune old entries with Clean history on the Synchronizations tab — that action is not available on History itself.