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 run Shipwright in a network-restricted environment I want to verify that HTTP proxy environment variables are present in build pods if a cluster-wide proxy is present.

Background (Required)

<Describes the context or background related to this story>

OpenShift Pipelines provides support for injecting *_PROXY environment variables in network restricted environments. See doc.

We need to verify that this behavior works for Shipwright builds that generate Tekton objects (TaskRuns)

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>

TBD

Dependencies

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

TBD

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>

• Shipwright builds succeed if a cluster-wide HTTP proxy is enabled.

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