Story (Required)

As a Red Hat engineer trying to release source-to-image I want to set up the correct EC contract checks for the s2i container image.

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

Components and applications on Konflux default to using a fairly straighforward EC policy. We need to configure the application to use a more stringent EC policy for Red Hat products.

Out of scope

<Defines what is not included in this story>

• Resolving EC contract violations. See BUILD-979
• Releasing s2i. See BUILD-980
• CI using integration test scenarios.

Approach (Required)

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

• Enable the source image parameter in the "on pull request" and "on push" Konflux pipeline. See https://docs.google.com/document/d/1bKE4pmrufEb1QROo7XhMVEmUClc--WtAmX1__rxNscc/edit#heading=h.ctzjiz7beb3i
• Create a new release plan tenant configuration for the "rh-openshift-builds-tenant" namespace: https://github.com/redhat-appstudio/tenants-config. See onboarding doc for more info.
• Verify that the EC integration test scenario functions correctly.

Dependencies

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

• Onboard s2i to Konflux: BUILD-978

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>

• EC policy for Red Hat Products is used for the enterprise contract integration test.
• Source containers built as part of Konflux build process.
• EC violations documented for remediation in BUILD-979

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