External Service Templates
An External Service Template defines the schema — the set of named variables — that any instance of a given type of external service will have. For example, a PostgreSQL template might define variables such as Host, Port, Username, and Password. Each External Service created from this template will hold its own values for those variables.
Role in the external service workflow
In the Component Detail, you add an External Service Template as a Connected Service binding — this declares that the component requires a service of this type at deployment time. No concrete instance is assigned here, only the binding type.
The actual External Service instance to use is then assigned per environment in the Deployment Configuration → Connected Services. This keeps the component decoupled from any specific environment's service instance and its values.
Permission separation
A key purpose of this feature is separating two distinct permissions:
- Who can configure which external service instance is used by a component
- Who can see the actual values (credentials, URLs) stored in that instance
A user who can assign an External Service to a component in its configuration does not automatically gain access to view the sensitive values stored in that External Service. Permissions on templates and permissions on service instances are managed independently.
What You Can Do
| Action | Description |
|---|---|
| List External Service Templates | Browse and search all external service templates |
| External Service Template Detail | View template variables and the components using this template |
| Delete External Service Template | Permanently remove a template |
| Permissions | Manage who can access and modify the template |