External services this deployment integrates with. Manage opens an integration's own admin page; Settings edits its runtime configuration. Kind says what the integration does for members: a provisioning integration creates and manages member resources, a payment integration handles billing. Registry status is an operator-managed record, not a live health or connectivity check; Configuration reflects whether the required keys below actually resolve to a value.
{{ if .Error }}No integrations registered.
| Integration | Registry status | Configuration | Kind | Operations | Resource keys | |
|---|---|---|---|---|---|---|
| {{ .DisplayName }} {{ .Slug }} | {{ if eq .Status "active" }} Active {{ else }} {{ .Status }} {{ end }} | {{ if not .Configured }} Not configured {{ else }} — {{ end }} | {{ .Kind }} | {{ range .Operations }}{{ . }}{{ end }} {{ if eq (len .Operations) 0 }}—{{ end }} |
{{ range .ResourceKeys }}{{ . }}{{ end }}
{{ if eq (len .ResourceKeys) 0 }}—{{ end }}
|
{{ if .SurfacePath }} Manage {{ end }} {{ if .SettingsPath }} Settings {{ end }} {{ if and (not .SurfacePath) (not .SettingsPath) }} — {{ end }} |
{{ len .Integrations }} integration(s) · driven by the provider registry. Non-secret settings can be overridden from each Settings page; secrets stay in the environment.
{{ end }} {{ if .Orphans }}Stored configuration overrides whose key matches no installed integration — left behind by a removed integration or a retired key. They have no effect; remove them when no longer wanted.
| Key | Value | |
|---|---|---|
{{ .Key }} |
{{ .Value }} |