tektoncd / tektoncd/operator

Self-signed certificates for Git resolver

Open
#1,614 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

kind/feature lifecycle/stale
Dominant language
Go
Stars
608
Forks
263
Avg merge
1d 3h
Merged PRs (30d)
125

Description

Feature request
Use case
  • We have a bitbucket repo hosted inside the org
  • The bitbucket server host has a self-signed cert
  • Can there be an option to pass self-signed certs to the git resolver ? Maybe using an env var (like NODE_EXTRA_CA_CERTS)?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the Git resolver and its certificate configuration, then compare the requested self-signed-certificate option with NODE_EXTRA_CA_CERTS for the Bitbucket use case. Done means the resolver supports the requested certificate configuration and the behavior is covered by an appropriate test.

Written by the indexing model from the issue text.

Assessment

Tech stack
git, go
Domain
networking, security
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.