Story (Required)

<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?>

As a developer trying to build images on specific nodes I want to set the node selectors on a BuildRun through the shp command line.

Background (Required)

<Describes the context or background related to this story>

With BUILD-1149, Shipwright will expose options that let builds be scheduled using node selectors. The shp command line should provide a simple user experience that lets developers set the node selectors on a `BuildRun`.

Upstream issue: shipwright-io/cli#260

Out of scope

<Defines what is not included in this story>

• Hardening guideline.
• Support for other scheduling options specified in SHIP-0039

Approach (Required)

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

Dependencies

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

• BUILD-1149 - Build API needs to provide/expose the node selectors.

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>

• Developers can set the node selector on a build through the `shp` CLI.
• CLI flag is self-documenting through `--help` command.
• Release note for new flag provided.
• Upstream documentation provided for the new CLI option (maybe?).
• CLI flag documented in Red Hat docs (maybe?)

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