-
Story
-
Resolution: Done
-
Normal
-
None
-
None
-
3
-
False
-
None
-
False
-
tkn pac resolve now supportg the flag v1beta1 to let users export pac pipelinerun on clusters that doesn't support v1
-
-
Story (Required)
Pipelines as Code tkn pac resolve -f currently output pipelinerun as v1, on some older cluster which doesn't run v1 yet it should be easy to apply pac pipelinerun in there even if v1 is not supported.
Background (Required)
<Describes the context or background related to this story>
Out of scope
<Defines what is not included in this story>
Approach (Required)
tkn pac resolve --v1beta1 -f ..... will output as v1beta1 the pipelinerun using tektoncd/pipeline converters.
(or -B for short of v1beta1)
Dependencies
<Describes what this story depends on. Dependent Stories and EPICs should be linked to the story.>
Acceptance Criteria (Mandatory)
<Describe edge cases to consider when implementing the story and defining tests>
<Provides a required and minimum list of acceptance tests for this story. More is expected as the engineer implements this story>
INVEST Checklist
Dependencies identified
Blockers noted and expected delivery timelines set
Design is implementable
Acceptance criteria agreed upon
Story estimated
Legend
Unknown
Verified
Unsatisfied
Done Checklist
- Code is completed, reviewed, documented and checked in
- Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
- Continuous Delivery pipeline(s) is able to proceed with new code included
- Customer facing documentation, API docs etc. are produced/updated, reviewed and published
- Acceptance criteria are met