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

Improve Tekton Object Interface #875

Open
chitrangpatel opened this issue Jul 20, 2023 · 2 comments
Open

Improve Tekton Object Interface #875

chitrangpatel opened this issue Jul 20, 2023 · 2 comments
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale

Comments

@chitrangpatel
Copy link
Contributor

As highlighted in https://docs.google.com/document/d/1IPE_xycMZ7I2ni98wPLFogY5xJEREdXuYwOuPnPL5Po/edit, when adding support for v1 objects, we need to replicate usage in a lot of files which is going to be tedious. We will need to keep support for v1beta1 around as well. It is unreasonable to keep two copies of all the functions that rely on v1beta1 types.

We use the tekton object interface quite a bit but its still not as heavily utilized in our formatting logic as it should be. This issue wants to investigate and improve the Tekton Object interface so that it can be utilized more heavily in our codebase.

@chitrangpatel chitrangpatel added the kind/feature Categorizes issue or PR as related to a new feature. label Jul 20, 2023
@chitrangpatel
Copy link
Contributor Author

/assign @lcarva

@tekton-robot
Copy link

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.

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/stale
Projects
None yet
Development

No branches or pull requests

3 participants