tektoncd / tektoncd/pipelines-as-code
`tkn-pac resolve` with private remote HTTP URLs
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 214
- Forks
- 144
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 27
Description
Hi,
I use PAC with a GitHub Enterprise instance and task references like
pipelinesascode.tekton.dev/task: https://ghe.com/org/repo/blob/main/task.yaml
While these work fine in the cluster environment , I cannot get them to work with tkn-pac resolve for testing.
Using tkn-pac resolve -f run.yaml results in
Error: error getting remote task from pipelinerun annotations: remote task from uri: https://ghe.com/org/repo/blob/main/task.yaml cannot be parsed as a kubernetes resource: yaml: line 32: mapping values are not allowed in this context
I have to use the raw URLs, which have a constantly changing token ?token=XXX appended in GHE, or replace all references with local references. Both solutions are not really practical to work with. Adding a provider token with -t does not seem to help either.
Is this expected or is there a solution I am missing?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the failure with tkn-pac resolve -f run.yaml and the private GitHub Enterprise task URL described in the issue. Start by tracing remote task retrieval, Kubernetes resource parsing, and the -t provider-token path; done means private remote task references resolve without requiring changing raw URLs or local replacements.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, go, kubernetes
- Domain
- ci-cd, cli, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100