Document PipelineResource's Alpha State #2447
Conversation
ghost
requested review from
googlebot
added
the
cla: yes
tekton-robot
added
the
size/M
|
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 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
| @@ -1048,6 +1056,70 @@ Data, | |||
| } | |||
| ``` | |||
|
|
|||
There was a problem hiding this comment.
It would also be helpful to include a section on how to use the API in the meantime. What are the recommended ways to use Tasks and Pipelines now, if you were relying on PipelineResources before?
Maybe this is already covered in a v1alpha to beta migration guide.
There was a problem hiding this comment.
Good catch, it's covered there and I've added links to it.
During the release of Pipelines' Beta we communicated the fact that PipelineResources are not being promoted along with other types but we didn't include any extensive commentary to support that decision. This commit adds a description of the problems that remain with PipelineResources, along with possible next steps that the project might take with them.
|
/test pull-tekton-pipeline-build-tests |
|
/lgtm |
afrittoli
added
the
kind/documentation
Changes
Fixes #1369
During the release of Pipelines' Beta we communicated the
fact that PipelineResources are not being promoted along
with other types but we didn't include any extensive
commentary to support that decision.
This commit adds a description of the problems that remain
with PipelineResources, along with possible next steps
that the project might take with them.
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.
Double check this list of stuff that's easy to miss:
cmddir, please updatethe release Task to build and release this image.
Reviewer Notes
If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.