Using PaC's `git_auth_secret` to Avoid Rate Limiting

Wed, 30 Jul 2025 00:00:00 +0000

Using PaC’s `git_auth_secret` to Avoid Rate Limiting #

When Tekton pipelines fetch resources like Tasks or Pipelines from a Git repository using the git resolver, frequent unauthenticated requests can lead to rate limiting from your Git provider. For private repositories, this fetching would fail entirely without authentication.

Pipelines-as-Code (PaC) solves this elegantly by automatically generating a temporary, scoped authentication token for each PipelineRun. This token is stored in a Kubernetes Secret, and its name is made available to your PipelineRun through the built-in {{ git_auth_secret }} variable.

OpenShift Pipelines 1.15 PAC release

Mon, 01 Jan 0001 00:00:00 +0000

OpenShift Pipelines 1.15 presents several new enhancements to Pipelines-as-Code. Below are the key updates.

Much improved GitOps Commands #

These commands allow you to make quick comments on a pull request to restart a PipelineRun through Pipelines-as-Code.

Commonly used commands include /test pipelinerun to rerun a specific PipelineRun, or /retest to rerun all PipelineRuns.

Trigger PipelineRuns Irrespective of Annotations #

Previously, to re-trigger PipelineRuns, they had to match specific annotations such as pipelinesascode.tekton.dev/on-event set to pull_request. Now, this constraint is removed, allowing you to trigger any PipelineRuns with /test regardless of their annotation status. This is particularly useful if you need to run a PipelineRun selectively before merging a PR, without it automatically consuming resources with each update.

Blog Posts on Pipelines as Code

Using PaC's `git_auth_secret` to Avoid Rate Limiting