Story (Required)

As a release engineer, trying to release a rpm containing the downstream version of ArgoCD core manifests, I have to include the new component microshift-gitops of type RPM to the GitOps Product configuration.

Background (Required)

Create an RPM Containing ArgoCD core manifests with official OpenShift GitOps Downstream container images. To build this RPM, downstream repository containing the manifests should be created and required branches need to be created.

Out of scope

None

Approach (Required)

Add a new component microshift-gitops of type RPM to the CPaaS Product configuration for OpenShift GitOps

Dependencies

None

Acceptance Criteria (Mandatory)

Add the component of type RPM microshift-gitops to the openshift-gitops product configuration

https://gitlab.cee.redhat.com/cpaas-products/openshift-gitops/

• gitops-nightly-1-rhel-8

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