-
Epic
-
Resolution: Done
-
Major
-
builds-1.0
-
None
-
Publish productized shp CLI
-
False
-
None
-
False
-
Not Selected
-
To Do
-
SECFLOWOTL-160 - Release Builds 1.1
-
0% To Do, 0% In Progress, 100% Done
-
S
-
Rejected
Epic Goal
- Make the `shp` command line easily to download for developers building applications on OpenShift.
Why is this important?
- The `shp` command line provides a build-centric user experience for developers. It is what developers want and expect from their tooling
- Productizing `shp` enables customers to use it outside of their desktops - ex, on CI systems outside of OpenShift.
Scenarios
- Developer downloads the CLI from the OpenShift console
- Developer downloads the CLI from a Red Hat owned website/domain.
Acceptance Criteria (Mandatory)
For GA announcement:
- Developer can download the CLI from our openshift cli mirror
- Documentation is updated to use the`shp` CLI instead of `oc` when possible.
- Technical enablement materials - update so CEE knows that customers will be downloading the CLI from the mirror and web console in the future
We can add the CLI to the OpenShift web console after GA announcement. We advertise web console download as "coming soon."
Dependencies (internal and external)
- Productized build of the `shp` golang binary
Previous Work (Optional):
Prior productization of the `tkn` binary.
Open questions:
- Do developers need to install the cli via yum/dnf on RHEL?
- No - we prefer OpenShift CLIs to be installed via the OpenShift console.
- Do we need the binary for all the platforms (linux/windows/darwin)?
- Current assumption - windows x86_64, darwin x86_64 and Apple Silicon, linux for x86_64, ARM, POWER, and Z
- If yes, how do we do QE/verify these?
- Should we also publish a container image for the `shp` binary? Ex for re-use in Tekton, Jenkins, GH Actions, etc.
- 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
- is related to
-
BUILD-1083 Publish shp CLI on OpenShift Console
- Dev Complete