Versioning Resources #918
Versioning Resources #918
Conversation
Today, we don't always bump versions of resources when updating them. The guideline has been to bump versions only when behavior changes, but it's hard to figure out when the behavior has changed (a change that could be trivial to one user could be meaningful to another). Not bumping resource versions when changing them causes issues where the resource definition becomes dependent on the time when it was applied by the user - which causes unexpected failures as described in tektoncd#784. This issue also came up as an issue where users cannot depend on the Step indices because they can change: tektoncd/community#572 (review). In TEP-0003, we already proposed that a policy for versioning of resources: https://github.com/tektoncd/community/blob/main/teps/0003-tekton-catalog-organization.md#versioning-resources In Catalog Working Group on 01/13/2022, we revisited that policy and: - agreed to follow the versioning policy - make it easier to bump resources (see tektoncd/plumbing#994) This change documents the versioning policy in the contributions guide. Fixes tektoncd#784
tekton-robot
added
the
size/XS
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: 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 |
tekton-robot
added
the
approved
|
if every time there is an update of a software which is in a task or we have to fix something in it (like documentation) we have to bump this may results a large number of tasks. It's maybe find and I am not sure if it's bad or not and could end up with some scaling issues. I wish we could use git as versioning system instead of directory structure but I am not sure how we can achieve that. so basically my vote is neutral :) |
|
Issues go stale after 90d of inactivity. /lifecycle stale Send feedback to tektoncd/plumbing. |
tekton-robot
added
the
lifecycle/stale
|
/lifecycle frozen |
tekton-robot
added
lifecycle/frozen
|
hoping the work in TEP-0101 will address this issue, so closing this pull request |
Changes
Today, we don't always bump versions of resources when updating them. The guideline has been to bump versions only when behavior changes, but it's hard to figure out when the behavior has changed (a change that could be trivial to one user could be meaningful to another).
Not bumping resource versions when changing them causes issues where the resource definition becomes dependent on the time when it was applied by the user - which causes unexpected failures as described in #784.
This issue also came up as an issue where users cannot depend on the Step indices because they can change: tektoncd/community#572 (review).
In TEP-0003, we already proposed that a policy for versioning of resources:
https://github.com/tektoncd/community/blob/main/teps/0003-tekton-catalog-organization.md#versioning-resources
In Catalog Working Group on 01/13/2022, we revisited that policy and:
catlin bumpfeature to bump catalog entries聽plumbing#994 - thanks @sbwsg 馃帀)This change documents the versioning policy in the contributions guide.
Fixes #784
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:
See the contribution guide for more details.