Skip to main content

Glossary & Troubleshooting

Glossary​

What this covers​

Definitions of the terms used across the ECP guides.

  • Deployment Pipeline — an ordered set of stages that a set of tenants promote configuration through.
  • Stage — a logical position within a Deployment Pipeline (e.g. Dev, SIT, UAT, Pre-Prod, Prod). Carries a colour used on badges.
  • Tenant — a Fenergo tenant registered in ECP, bound to one environment and holding configuration files.
  • Environment — a registered connection to a Fenergo platform region (a named API target with a base URL).
  • DCI (Dedicated Customer Instance) — an environment dedicated to a single customer, restricted by default.
  • Organisation — the container that holds Deployment Pipelines; access to it grants visibility of every Deployment Pipeline within.
  • Domain / sub-domain — the two-level grouping ECP uses to organise a tenant's configuration files.
  • Deploy — pushing whole configuration files from a source tenant to one or more targets.
  • Merge — applying selected paths from one tenant's config file into another.
  • Compare — read-only side-by-side inspection of two tenants' configuration.
  • API-triggered deployment — a deployment initiated via the API using an API key rather than through the ECP UI. Appears in the Activity Log and Past Deployments with an API tag.
  • API key — an organisation-scoped secret used to authenticate programmatic API calls to ECP.
  • Roles — Fenergo Admin, Admin, Member (see Prerequisites & access in the Introduction, and Admin → User Management for granting access).

Troubleshooting & FAQ​

Common questions and issues that span more than one feature. Feature-specific troubleshooting lives at the end of each guide.

FAQ​

Should I use Compare, Merge or Deploy? Compare to understand differences (read-only), Merge for selective path-by-path changes, Deploy to promote whole files forward. See Which tool do I use? in the Introduction.

Why can't I see any environments when adding a tenant? Your organisation hasn't been granted any. Environments are never visible by default — Fenergo must grant at least one to your organisation.

Why isn't my target tenant selectable in Deploy? Stage-promotion rules. Within a Deployment Pipeline, only later-stage tenants are eligible; cross-pipeline targets must be in a child pipeline's entry stage.

Why did some domains fail when I added a tenant? Usually incorrect API client credentials. Fix them in the target tenant, then refresh the affected domains from the tenant page.

Where do I see who changed what? The Activity Log — filter by event type, actor, domain, tenant or status, and export to CSV.