OSDOCS-19549: Instructions to enable plugins sans UI

[jseseCCS]

Version(s): 4.22

Issue: https://redhat.atlassian.net/browse/OSDOCS-19549

Link to docs preview:

QE review:

• QE has approved this change.

Additional information:

[openshift-ci-robot]

@jseseCCS: This pull request references OSDOCS-19549 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "5.0.0" version, but no target version was set.

Details

In response to this:

Version(s): 4.22

Issue: https://redhat.atlassian.net/browse/OSDOCS-19549

Link to docs preview:

QE review:

• QE has approved this change.

Additional information:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

Hi @jseseCCS. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Tip

We noticed you've done this a few times! Consider joining the org to skip this step and gain /lgtm and other bot rights. We recommend asking approvers on your previous PRs to sponsor you.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[jseseCCS]

@alimobrem @spadgett @logonoff Please review this first draft of the new module for "Enabling a dynamic plugin using the CLI"

Before you dig in, note that I made these assumptions so, of course, correct me if I'm wrong:

1. I assumed cluster-admin access is required to patch console.operator.openshift.io/cluster.
   Why: The Jira’s script patches a cluster-scoped resource with oc patch console.operator.openshift.io cluster .... The story never names a specific role/permission, so I used cluster-admin as the safest requirement that will actually let a customer run the patch.

2. I added generic prerequisites (plugin installed by Operator/Helm, ConsolePlugin CR exists) that reflect the script’s starting state.
   Why: The Jira describes “scripted operator installs” and “without using the UI,” and the script literally waits until a ConsolePlugin exists (until oc get consoleplugin ...). That means the plugin install must already have happened and must have created the ConsolePlugin CR before the enablement step can work.

3. I introduced a short verification step (oc get ... -o jsonpath='{.spec.plugins}') plus a note about console refresh time since those details are not called out.
   Why: The Jira script changes spec.plugins, but it doesn’t give users a clean “confirm it worked” command or set expectations for when they’ll see the result. I added a quick jsonpath check because it matches what the script already reads (-o jsonpath='{.spec.plugins}'), and I added the refresh/timing note because users will immediately ask when the console reflects the config change.

Again, we can remove or change any of these.

Eager for your feedback