Skip to main content
Video tutorial · 1:12

Dependency graph

Every certificate participates in a web of upstream and downstream relationships: ACME account → cert, zone → cert, cert → distributions → targets. The dependency graph visualizes that web and — more practically — powers the safety checks that refuse destructive operations when something downstream still relies on the target.

Upstream (what the cert depends on)​

  • Issuer — one ACME account, one MSCA connection or one CA connection.
  • DNS zone → its DNS credential (automated DNS validation).
  • Organization — the OV/EV subject record, when one is selected.
  • Certificate policy (if enabled on the project) — not a graph node, but an enforcement boundary that shapes what a new cert can be.

Downstream (what depends on the cert)​

  • Distributions — zero or more, each binding the cert to a module config.
  • Module configs and what they resolve to — targets, target groups, the module credentials they use, and the library PathSets / ActionSets they reference.
  • A reference that points at a record which no longer exists is drawn as a missing reference node, so a dangling id is visible instead of silently dropped.

The graph view​

  1. Open the certificate detail page.
  2. Switch to the Dependency Graph tab.
  3. A directed graph renders the certificate with its upstream and downstream nodes; edges are labelled with the relationship.

Safety checks​

Delete operations are refused while something still references the resource (the API answers 409 with the blocking references):

  • Deleting an ACME account, MSCA connection or CA connection is blocked while any certificate references it.
  • Deleting a DNS credential is blocked while any zone references it, which is in turn blocked while any certificate depends on the zone.
  • Deleting a target is blocked while it is a member of a target group or listed in a module config.
  • Deleting a module credential is blocked while a target or target group uses it as its credential, or a secret store authenticates with it.
  • Deleting a certificate is blocked while any distribution references it, or while one of its jobs is actively running (pending jobs are cancelled as part of the delete).

The block is soft: the UI explains the blocking reference(s) and lets you jump to them. There is no force-delete. If you want to decommission an upstream resource, repoint the dependants first.

Query via API​

# The certificate's graph (nodes + edges)
GET /api/v1/projects/{projectId}/certificates/{id}/graph

# What would block deleting a resource (the same check the DELETE runs)
GET /api/v1/projects/{projectId}/dependencies?type=<resource_type>&id=<resource_id>

The graph returns nodes and edges:

{
"nodes": [
{"id":"...", "type":"certificate", "label":"api.example.com", "status":"active"},
{"id":"...", "type":"acme_account", "label":"letsencrypt-prod"},
{"id":"...", "type":"distribution", "label":"web-fleet-ssh"}
],
"edges": [
{"source":"...", "target":"...", "label":"ACME Account"}
],
"generated_at": "..."
}

The dependency check returns, per blocking resource type, a count and a few sample names.

Common graph shapes​

  • Orphan cert: issuer + zones upstream, no distributions downstream. Worth reviewing — nothing deploys it. (Risk scoring does not flag this case.)
  • Shared target: one target referenced by many distributions (many certs land on one host). Deleting the target refuses until all are repointed.
  • Multi-module cert: one cert with SSH + Kubernetes + Vault distributions — three downstream edges, three separate rollback stories.

Troubleshooting​

"Cannot delete — N references"​

Open each blocking reference named in the error, repoint or delete it. Once every reference is cleared, the delete succeeds.

Graph shows a reference that should be gone​

Dependencies are computed on-read from current DB state — stale references come from real data. Check the named resource directly; often a soft-deleted record still carries the reference. Contact support with the resource IDs if the graph shows something the source-of-truth doesn't.

See also​

Video tutorial

Short, hands-on videos showing this feature working for real. English audio, English and Turkish subtitles. All video tutorials →

Certificate Detail — Chain of Trust, Timeline and Dependency GraphYouTube ↗