Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add URL Resolver #6920

Closed
zroubalik opened this issue Jul 11, 2023 · 8 comments · Fixed by #7250
Closed

Add URL Resolver #6920

zroubalik opened this issue Jul 11, 2023 · 8 comments · Fixed by #7250
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@zroubalik
Copy link

Feature request

Would be nice to add URL Resolver, that fetches Task/Pipeline directly from the URL. Pipelines as Code support this kind of resolver.

Use case

It useful to reference a task that is hosted on some remote URL or even in a git repo. Using Git Resolver on a large repository is not convenient, becase it takes a lot of time to fetch the whole repo and the use the file. If we can just reference the file by URL, the resolving will be much faster.

@zroubalik zroubalik added the kind/feature Categorizes issue or PR as related to a new feature. label Jul 11, 2023
@AlanGreene
Copy link
Member

When using the authenticated API the git resolver only fetches the specified file: https://tekton.dev/docs/pipelines/git-resolver/#authenticated-api

Does this work for your use case? If not can you elaborate on the issue(s) you're facing?

@zroubalik
Copy link
Author

zroubalik commented Jul 12, 2023

Authenticated API doesn't work for our usecase, as it would require another configuration that we don't want to deal with. At least that's my understanding that we would need to configure additional secrets and what not, right?

Also the documentation on https://tekton.dev/docs/pipelines/git-resolver/#authenticated-api is not very clear TBH. Are the Task & Pipelines Resolution examples complete? It would be nice if it really show everything that needs to be configured.

@tekton-robot
Copy link
Collaborator

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale with a justification.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle stale

Send feedback to tektoncd/plumbing.

@tekton-robot tekton-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 10, 2023
@vdemeester
Copy link
Member

/lifecycle frozen

@tekton-robot tekton-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Oct 10, 2023
@vdemeester
Copy link
Member

/assign @chmouel

@tekton-robot
Copy link
Collaborator

@vdemeester: GitHub didn't allow me to assign the following users: chmouel.

Note that only tektoncd members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

/assign @chmouel

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@chmouel
Copy link
Member

chmouel commented Oct 20, 2023

since I'd like to have Pipelines-as-Code using pipelines resolvers and bring feature parity I can take this on!

/assign

@vdemeester
Copy link
Member

/assign @chmouel

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants