External HTTP Service
Use an existing hosted HTTP dependency. Lifecycle does not build or deploy it.
An externalHttp Service defines an HTTP dependency that runs outside the
Lifecycle Environment. Lifecycle marks the Service ready without creating a
workload. It makes the configured endpoints available to dependent Services.
Schema
| Field | Required | Description |
|---|---|---|
defaultInternalHostname | Yes | Cluster-reachable fallback hostname used by other Services. |
defaultPublicUrl | Yes | Public fallback URL exposed for users and URL template variables. |
Use externalHttp as the nested key.
When to use it
Use externalHttp for a dependency with all these properties:
- a team outside Lifecycle manages it
- appears in Service resolution and generated variables
- has stable internal and public endpoints.
Do not use it for a Service that Lifecycle must build or deploy. Select
github, docker, helm, codefresh, or a different supported deployable
type.
Environment overrides
An Environment can point an eligible external HTTP Service at a different URL. Make sure that the user and applicable workloads can reach the new target. Lifecycle does not provision, monitor, or remove the external system.