-
Notifications
You must be signed in to change notification settings - Fork 563
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
v1
support and the future of tektoncd/catalog
#1146
Comments
Thanks @vdemeester! For 1, taking the example of golang catalog migration, the current selection of the resources to be migrated is in If we want to bump the API version to |
yes @QuanZhang-William, we should be bumping up the version of the resource |
@QuanZhang-William I think it really depends on what we want to support. We could state that anything going in |
Agreed. I think the question is that do we want to continue to maintain Supporting both WDYT? /cc @ywluogg |
Catalog WG summary: The verified catalogs will be started with |
Issues go stale after 90d of inactivity. /lifecycle stale Send feedback to tektoncd/plumbing. |
Stale issues rot after 30d of inactivity. /lifecycle rotten Send feedback to tektoncd/plumbing. |
/lifecycle frozen |
This issue is to discuss and track work around having
v1
API support for tasks in the catalog, in the light of the recent TEP around catalog:As of
tektoncd/pipeline
latest LTS release (0.44.x), we providev1
API for tekton pipeline's objects. This means, we can start publishingTask
s usingv1
. But as TEP-0079 state, we want to move towards having smaller, well written and supportedTask
s (and other resource) maintained, in thetektoncd-catalog
org. And let contributors share and maintain resources in their own Community Catalogs. Hence this issue.tektoncd-catalog
repository will switch tov1
there and marked as deprecated here./cc @tektoncd/catalog-maintainers @tektoncd/catalog-collaborators @QuanZhang-William @bobcatfish @jerop
The text was updated successfully, but these errors were encountered: