You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/en/connectors/architecture/index.mdx
+16-2Lines changed: 16 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -67,7 +67,7 @@ This API is very useful in practical applications, such as:
67
67
68
68
The implementation of the `Connectors API` is based on the underlying capabilities provided by the `ConnectorClass API`.
69
69
70
-
# ConnectorClass API
70
+
##ConnectorClass API
71
71
72
72
`ConnectorClass API` defines the APIs provided by specific types of tools.
73
73
@@ -78,10 +78,24 @@ Different types of tools can offer various API capabilities, for example:
78
78
79
79
Developers can define unique API capabilities for each `ConnectorClass`, and these capabilities will ultimately be exposed to clients through the `Connectors API`.
80
80
81
-
# Connectors CSI Driver
81
+
##Connectors CSI Driver
82
82
83
83
To facilitate easier utilization of Connectors-Proxy capabilities by K8S workloads, we can use the Connectors CSI Driver.
84
84
85
85
The Connectors CSI Driver can mount the rendered contents of the configuration file templates maintained within the ConnectorClass into the workload. The configuration file can include information for accessing the `Connectors Proxy`, enabling users to utilize Connectors Proxy capabilities with minimal modifications to their original scripts.
86
86
87
87
For more information, refer to [connectors csi driver](../concepts/connectors_csi.mdx)
88
+
89
+
## ResourceInterface
90
+
91
+
`ResourceInterface` is a standardized abstraction that defines how external resources (like Git repositories, OCI container images, artifact repositories) can be integrated into pipeline workflows.
92
+
93
+
When building CI/CD pipelines, users traditionally need to manually configure resource URLs, git branch/tag, OCI image tag, artifact repository, and authentication credentials for different external tools. This manual process is complex, error-prone, and makes pipeline configurations tightly coupled to specific tool instances.
94
+
95
+
ResourceInterface solves this by providing standard resource abstraction like "GitCodeRepository", "OCIArtifact", and "MavenArtifact". Instead of manually entering URLs like `https://github.com/myorg/myapp.git`, users can select a connector, browse resources through the UI, and the system automatically generates the correct configuration and credentials for the pipeline.
96
+
97
+
This approach provides a consistent, user-friendly experience across different tools while maintaining flexibility to support various implementations.
98
+
99
+
For more information, refer to [ResourceInterface](../concepts/resource_interface.mdx).
100
+
101
+
If you want to integrate Connector in your custom Pipeline or Task, please refer to <ExternalSiteLinkname="pipelines"href="/pipelines/concepts/integrate_with_connector.html"children="Pipeline Integration" />
0 commit comments