Story (Required)

See parent epic for high level details. GITOPS-5636 is a prerequisite for this story. See list of helpful additional resources on parent epic.

Our goal is to add and release Argo Rollouts CLI via OpenShift GitOps v1.20, in a similar way that we built/releases Argo CD CLI in v1.19.

Acceptance Criteria

AFAICT, this is the remaining work.

Add Argo Rollouts CLI build to https://github.com/rh-gitops-midstream/release, specifically the 'main' branch.

• See example of other CLIs we are building:
  • 'clis/argocd' directory

Add Component for argo rollouts cli 'argo-rollouts-cli'. See the other cli-based Components that exist within Konflux and/or in konflux-release-data:

• https://gitlab.cee.redhat.com/releng/konflux-release-data/-/blob/main/tenants-config/cluster/stone-prd-rh01/tenants/rh-openshift-gitops-tenant/gitops-main.yaml?ref_type=heads#L273

Work with Siddhesh/Neus to determine where we should update the ReleasePlanAdmission:

• Here is the RPA for 1.19 in 'konflux-release-data' repo: config/stone-prd-rh01.pg1f.p1/product/ReleasePlanAdmission/rh-openshift-gitops/gitops-clis-1-19-prod.yaml
  • Obviously we don't want to update 1.19 RPA as it has already released.
• But where do we need to update for future releases?

I don't believe we need to update the ReleasePlan, as it already points the RPA.

Anything else we need to update?

Once the above is updated, ensure that the Argo Rollouts CLI build passes.

Ask Siddhesh/Neus if there is a way for us to test the Argo Rollouts CLI release process before the actual v1.20 release. If there is, test it.