Story (Required)

As a developer trying to release rhel9 image for S2I, I want create a new CPE id for the product.

Background (Required)

Currently the CPE ID exists for rhel8 image of S2I, and since we want to release both rhel8 and rhel9 images, we'll need a new CPE ID for the rhel9 image.

Out of scope

Approach (Required)

• Create a new CPE id for S2I in this repo, https://gitlab.cee.redhat.com/prodsec/product-definitions/-/blob/master/data/developer/ps_modules.json?ref_type=heads#L621
• Configure the CPE id in Konflux release configurations repo, https://gitlab.cee.redhat.com/releng/konflux-release-data/-/blob/main/prodsec/ocp-tools-s2i.yaml?ref_type=heads

Dependencies

NA

Acceptance Criteria (Mandatory)

• CPE ID created by releng team
• CpeID configured in Konflux prodsec repo.

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