Story (Required)

As a developer trying to use Shipwright to build containers I don't want to add special annotations to secrets that contain build-related credentials.

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

In the early days of Shipwright, we required secrets to have an annotation added to them in order to update the "registered" state of Build objects. As the project has evolved, the community feels that this feature may not be needed any more because the controller has an in-memory cache of all secrets on the cluster.

Out of scope

<Defines what is not included in this story>

• Removing registration validations on the Build object

Dependencies

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

None

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>

• Secrets used in a build do not need special annotations - updates to secrets in a build will re-reconcile the "registered" state.

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