tektoncd/pipeline

TEP-161: Resolver cache implementation follow-up tasks

Offen

#9.228 geöffnet am 13.12.2025

 (4 Kommentare) (0 Reaktionen) (1 zugewiesene Person)Go (1.943 Forks)auto 404
area/testinghelp wantedkind/cleanupkind/featurekind/tep

Repository-Metriken

Stars
 (9.013 Sterne)
PR-Merge-Metriken
 (Durchschn. Merge 9T 3h) (137 gemergte PRs in 30 T)

Beschreibung

Description

This is a tracking issue for follow-up tasks related to the resolver cache implementation introduced in #9051. The resolver cache provides a framework for caching resolved remote resources with configurable modes (always, never, auto), TTL, and LRU eviction.

The sub-issues below address configuration improvements, test coverage, and future-proofing identified during code review.

How to contribute

When working on one of these tasks:

  1. Assign yourself the sub-issue
  2. Open PR with fix and reference the sub-issue with "Fixes #"
  3. Once your PR is merged, your issue will be closed and the list below updated

[!IMPORTANT]
An important note on AI tools use. If you use AI then please review and test its code thoroughly before opening a PR and add a small note in the PR description that you used AI. This will help me during review.

References:

Questions

Contact me on the Tekton Slack if you have questions. I check Slack regularly. Or start a discussion in the comment section of the issues.


/kind cleanup /help-wanted

Contributor Guide