tektoncd/pipeline

TEP-161: Resolver cache implementation follow-up tasks

Ouverte

#9 228 ouverte le 13 déc. 2025

 (4 commentaires) (0 réaction) (1 personne assignée)Go (1 943 forks)auto 404
area/testinghelp wantedkind/cleanupkind/featurekind/tep

Métriques du dépôt

Stars
 (9 013 étoiles)
Métriques de merge PR
 (Merge moyen 9j 3h) (137 PRs mergées en 30 j)

Description

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

Guide contributeur