External Registry
ExternalRegistry
Defines a connection to a third-party artifact registry.
Does not directly provision infrastructure, but provides the URL and authentication mechanics required for the engine (e.g., CI/CD workers or GKE nodes) to pull images or packages from sources like Docker Hub or Quay.io.
| Property | Type | Description |
|---|---|---|
| apiVersion | string | |
| kind | string | |
| metadata | map | |
| spec | Spec |
Spec
Houses the connection details and authentication for the external registry. Instructs the execution engine on which protocol (e.g., DOCKER, HELM) and authentication method to use when communicating with the target URL.
| Property | Type | Description |
|---|---|---|
| enabled | bool | Determines the operational status of the registry configuration. If true, this configuration is evaluated and actively mapped by the engine. If false, it is entirely omitted from the execution graph. |
| description | string | Provides a localized, natural-language explanation of this registry's role. Injected into the search context to drastically improve AI assistant reasoning and metadata categorization for human operators. |
| type | string | Dictates the specific artifact format hosted by the external registry. Evaluated by the engine to determine exactly which underlying connection protocol and credential injection pattern (e.g., 'docker login', 'helm repo add') is required during execution. |
| url | string | Specifies the authoritative base endpoint of the target external registry. Processed by the execution engine to establish network routing for dependency resolution, artifact pulling, and security scanning operations. |
| authentication | string | Defines the mechanism required to negotiate access with the target endpoint. Instructs the engine on how to securely resolve and inject credentials during execution, supporting patterns like bearer tokens, SSH keys, or basic authentication. |