-
Notifications
You must be signed in to change notification settings - Fork 102
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
[TEP-0110] Add an Endpoint for Fetching a Raw Tekton Resource YAML File #539
Conversation
/assign @jerop |
1f943c4
to
377e8d3
Compare
cc @vinamra28 |
/assign @vinamra28 Hi Vinamra, several points in mind.. just correct me: located the endpoint under the service
original TEP didn't mention a yaml file will be required for the return vals. use a String as return type at this moment, thinking perhaps this wouldn't work and some formatting logic I need to add right? like converting the string (or []bytes) in to a formatted yaml file |
/retest |
/unassign |
cc @ywluogg |
d529ac1
to
ed4cb07
Compare
ce2538c
to
e84f94b
Compare
As for decoupling the catalog organization and tekton resource references, a new endpoint is added to offer a resource request url only related to {catalog}, {kind}, {resourceName}, {resourceVersion} which can be directly applied with kubectl apply -f domain/v1/{catalog}/{kind} /{name}/{version}/raw.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PR looks good. Thanks @austinzhao-go 🙂
/cc @PuneetPunamiya @piyush-garg
/meow
In response to this:
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. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: vdemeester, vinamra28 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thank you @austinzhao-go!
/lgtm
…on Catalog Prior to this change, the installation instructions directly uses the resource urls in the Catalog repo, which results in tight coupling between the organization and how users fetch resources (as described in TEP-0110). This commit updates the installation guide to install Tekton Catalog resources via Tekton Hub by leverage the new Hub Api[tektoncd/hub#539]. This change decouples the Tekton Catalog organization from resouces resolution, which enables Tekton Catalog reorganization.
Prior to this change, the installation instructions directly use the resource urls in the Catalog repo, which results in tight coupling between the organization and how users fetch resources (as described in TEP-0110). This commit updates the installation guide to install Tekton Catalog resources via Tekton Hub Api: tektoncd/hub#539 This change decouples the Tekton Catalog organization from resouces resolution, which enables Tekton Catalog reorganization.
Prior to this change, the installation instructions directly use the resource urls in the Catalog repo, which results in tight coupling between the organization and how users fetch resources (as described in TEP-0110). This commit updates the installation guide to install Tekton Catalog resources via Tekton Hub Api: tektoncd/hub#539 This change decouples the Tekton Catalog organization from resouces resolution, which enables Tekton Catalog reorganization.
Prior to this change, the installation instructions directly use the resource urls in the Catalog repo, which results in tight coupling between the organization and how users fetch resources (as described in TEP-0110). This commit updates the installation guide to install Tekton Catalog resources via Tekton Hub Api: tektoncd/hub#539 This change decouples the Tekton Catalog organization from resouces resolution, which enables Tekton Catalog reorganization.
Prior to this change, the installation instructions directly use the resource urls in the Catalog repo, which results in tight coupling between the organization and how users fetch resources (as described in TEP-0110). This commit updates the installation guide to install Tekton Catalog resources via Tekton Hub Api: tektoncd/hub#539 This change decouples the Tekton Catalog organization from resouces resolution, which enables Tekton Catalog reorganization.
Prior to this change, the installation instructions directly use the resource urls in the Catalog repo, which results in tight coupling between the organization and how users fetch resources (as described in TEP-0110). This commit updates the installation guide to install Tekton Catalog resources via Tekton Hub Api: tektoncd/hub#539 This change decouples the Tekton Catalog organization from resouces resolution, which enables Tekton Catalog reorganization.
Prior to this change, the installation instructions directly use the resource urls in the Catalog repo, which results in tight coupling between the organization and how users fetch resources (as described in TEP-0110). This commit updates the installation guide to install Tekton Catalog resources via Tekton Hub Api: tektoncd/hub#539 This change decouples the Tekton Catalog organization from resouces resolution, which enables Tekton Catalog reorganization.
Changes
/kind feature
The related TEP:
TEP-0110: Decouple Catalog Organization and Resource Reference
Add an Endpoint for Fetching a Tekton Resource YAML File as:
domain/v1/resource{catalog}/{kind}/{name}/{version}/raw
This change will support a user to directly apply the served yaml file to a cluster, like:
kubectl apply -f https://hub.tekton.dev/tekton/task/buildpacks/0.4/raw
TODO
domain/v1/resource/tekton/task/git-clone/0.5/raw
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:
make api-check
(api-check met an existing error. the issue was raised to be tracked and fixed as [Fix] Failed API Tests
make api-check
#549))make ui-check
See the contribution guide for more details.