ResolutionRequest

API reference for the ResolutionRequest v1beta1 resource

ResolutionRequest is at v1beta1 stability level.

A ResolutionRequest is used to request the content of a Tekton resource from a remote location, such as a git repository or OCI registry.

Resource Definition

apiVersion · string · required

resolution.tekton.dev/v1beta1

kind · string · required

ResolutionRequest

metadata · ObjectMeta · required

Standard Kubernetes metadata.

spec · ResolutionRequestSpec · required

Specification for the resolution request.

status · ResolutionRequestStatus

Status of the resolution request.

ResolutionRequestSpec

params · []Param

Runtime parameters passed to the resolver to help locate the resource.

Common parameters vary by resolver:

Git Resolver:

• url - Repository URL
• revision - Branch, tag, or commit SHA
• pathInRepo - Path to the resource file

Bundle Resolver:

• bundle - OCI bundle reference
• name - Name of the resource in the bundle
• kind - Kind of resource (Task, Pipeline)

Hub Resolver:

• name - Resource name
• version - Resource version
• catalog - Catalog name
• kind - Resource kind

See Parameter Types for details.

url · string

Runtime URL passed to the resolver. This is an alpha feature.

ResolutionRequestStatus

conditions · []Condition

Conditions describing the resolution state.

Show Condition fields

type · string

Primary type: Succeeded

status · string

• True - Resolution succeeded
• False - Resolution failed
• Unknown - Resolution in progress

reason · string

Reason for the current state.

message · string

Human-readable message.

data · string

The resolved content of the requested resource, inline in the ResolutionRequest.

This is typically a YAML representation of a Task or Pipeline.

refSource · RefSource

Source reference of the remote data including URL, digest, and entrypoint.

Show RefSource fields

uri · string

URI of the source (e.g., git repo URL or OCI image reference).

digest · map[string]string

Content digest for verification.

entryPoint · string

Entry point within the source (e.g., file path).

Resolvers

Tekton includes several built-in resolvers:

Git Resolver

Resolves resources from git repositories.

resolver: git
params:
  - name: url
    value: https://github.com/tektoncd/catalog.git
  - name: revision
    value: main
  - name: pathInRepo
    value: task/git-clone/0.9/git-clone.yaml

Bundle Resolver

Resolves resources from OCI bundles.

resolver: bundle
params:
  - name: bundle
    value: gcr.io/tekton-releases/catalog/upstream/git-clone:0.9
  - name: name
    value: git-clone
  - name: kind
    value: Task

Hub Resolver

Resolves resources from Artifact Hub.

resolver: hub
params:
  - name: catalog
    value: tekton-catalog-tasks
  - name: type
    value: artifact
  - name: kind
    value: task
  - name: name
    value: git-clone
  - name: version
    value: "0.9"

Cluster Resolver

Resolves resources from the same Kubernetes cluster.

resolver: cluster
params:
  - name: kind
    value: Task
  - name: name
    value: my-task
  - name: namespace
    value: default

Example

ResolutionRequests are typically created automatically when using remote resolution in TaskRuns or PipelineRuns:

apiVersion: tekton.dev/v1
kind: TaskRun
metadata:
  name: git-clone-run
spec:
  taskRef:
    resolver: git
    params:
      - name: url
        value: https://github.com/tektoncd/catalog.git
      - name: revision
        value: main
      - name: pathInRepo
        value: task/git-clone/0.9/git-clone.yaml

This creates a ResolutionRequest in the background to fetch the Task definition.