Author Catalog Resources
artifacthub-shim indexes Tekton resources from filesystem and Git catalog
sources. A catalog can contain Task, Pipeline, and StepAction resources.
Each resource is versioned by directory and exposed through the DevOps Hub UI,
Artifact Hub-compatible APIs, and Tekton resolver: hub.
Directory Layout
Use this layout for a catalog repository:
Rules:
- The top-level directory is the lowercase resource kind:
task,pipeline, orstepaction. - A version directory must contain one YAML manifest named after the resource.
metadata.namemust match the package directory name.metadata.labels["app.kubernetes.io/version"]should match the version directory.README.mdis recommended because it is shown in UI detail pages.- Optional resource directories such as
config/can contain ConfigMaps that are synchronized throughextraResourcesinstead of indexed as catalog packages. Use this for supporting resources such as overview templates and tool image selector options. See Configure Custom Git Repositories, Customize Task Overview with Templates, and Add Custom Task Images to Selector.
Required Metadata
Every indexed resource should include a description and version metadata:
Keep ClusterTask out of new catalog content. Tekton Pipelines v1 uses
namespaced Task resources.
Resolver References
Use type: artifact when resolving resources through artifacthub-shim.
Built-in catalog names:
The built-in StepAction catalog is registered only when the packaged catalog
contains a stepaction/ directory.
For complete resolver syntax, see Consume Resources with the Hub Resolver.
Validation Checklist
- The path follows
<kind>/<name>/<version>/<name>.yaml. - The manifest name and directory name match.
- The version label matches the version directory.
spec.descriptionis present and useful.- Parameters, workspaces, and results have descriptions.
- Samples and README examples use
type: artifact. - Additional ConfigMaps that must be synced to the cluster have
artifacthub-shim.alauda.io/import: "true".