Epic Goal

• Make the `shp` command line easily to download from OpenShift Console

Why is this important?

• To simply access to shp cli

Scenarios

1. Developer downloads the CLI from the OpenShift console
2. Developer downloads the CLI from a Red Hat owned website/domain.

Acceptance Criteria (Mandatory)

• A link to shp CLI is available on Console CLI page

Dependencies (internal and external)

TBD

Previous Work (Optional):

TBD

Open questions:

1. Do developers need to install the cli via yum/dnf on RHEL?
   1. No - we prefer OpenShift CLIs to be installed via the OpenShift console.
2. Do we need the binary for all the platforms (linux/windows/darwin)?
   1. Current assumption - windows x86_64, darwin x86_64 and Apple Silicon, linux for x86_64, ARM, POWER, and Z
   2. If yes, how do we do QE/verify these?
3. Should we also publish a container image for the `shp` binary? Ex for re-use in Tekton, Jenkins, GH Actions, etc.
   1. Current assumption - this is a nice to have, potentially take this up as a future story/epic.

Done Checklist

• Acceptance criteria are met
• Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
• User Journey automation is delivered
• Support and SRE teams are provided with enough skills to support the feature in production environment