Story (Required)

As a developer trying to build containers with Shipwright I want an updated version of the `shp` CLI.

<Describes high level purpose and goal for this story. Answers the questions: Who is impacted, what is it and why do we need it? How does it improve the customer’s experience?>

Background (Required)

<Describes the context or background related to this story>

`shp` CLI v0.14.0 brings the new `--params` flag, which is essential for working with builds/build strategies.

Out of scope

<Defines what is not included in this story>

TBD

Approach (Required)

<Description of the general technical path on how to achieve the goal of the story. Include details like json schema, class definitions>

• Release will need to happen via CPaaS.

Dependencies

<Describes what this story depends on. Dependent Stories and EPICs should be linked to the story.>

• Upstream CLI release v0.14.0

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>

• CLI rebased and updated downstream.
• Any release engineering work.

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