CONSOLE-4690: Add Manifest tab to the ConsolePlugin resource details page

[Leo6Leo]

Description

Implement the manifest tab for the ConsolePlugin details page using PatternFly 6's CodeEditor component.

The example impacted page path is http://localhost:9000/k8s/cluster/console.openshift.io~v1~ConsolePlugin/console-demo-plugin/plugin-manifest

Steps to test

Prerequisite:
Please make sure you build both front end and backend before proceeding.

1. Build the console-demo-plugin

cd dynamic-demo-plugin
yarn install
yarn build

2. Run the plugin http server on port 9001

yarn http-server

3. Create the consoleplugin Custom Resource

oc apply -f oc-manifest.yaml

4. Configure the cluster to be no_auth for development purposes

source ./contrib/oc-environment.sh 

5. Run the bridge server

 ./bin/bridge -plugins=console-demo-plugin=http://localhost:9001 -i18n-namespaces=plugin__console-demo-plugin

6. Visit the following url to see the difference
   http://localhost:9000/k8s/cluster/console.openshift.io~v1~ConsolePlugin/console-demo-plugin/plugin-manifest

Demo

Before

---

After

[Leo6Leo]

/cc @logonoff

[logonoff]

looks good! just a few more nits

[logonoff]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Leo6Leo, logonoff

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• frontend/OWNERS [logonoff]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[logonoff]

/label tide/merge-method-squash

[Leo6Leo]

/retest

[Leo6Leo]

/retest-required

[logonoff]

/retest

[Leo6Leo]

/jira refresh

[openshift-ci-robot]

@Leo6Leo: No Jira issue is referenced in the title of this pull request.
To reference a jira issue, add 'XYZ-NNN:' to the title of this pull request and request another refresh with /jira refresh.

In response to this:

/jira refresh

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.

[Leo6Leo]

/jira refresh

[openshift-ci-robot]

@Leo6Leo: No Jira issue is referenced in the title of this pull request.
To reference a jira issue, add 'XYZ-NNN:' to the title of this pull request and request another refresh with /jira refresh.

In response to this:

/jira refresh

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.

[logonoff]

/retitle CONSOLE-4690: Add Manifest tab to the ConsolePlugin resource details page

[openshift-ci-robot]

@Leo6Leo: This pull request references CONSOLE-4690 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 "4.20.0" version, but no target version was set.

In response to this:

Description

Implement the manifest tab for the ConsolePlugin details page using PatternFly 6's CodeEditor component.

The example impacted page path is http://localhost:9000/k8s/cluster/console.openshift.io~v1~ConsolePlugin/console-demo-plugin/plugin-manifest

Steps to test

Prerequisite:
Please make sure you build both front end and backend before proceeding.

1. Build the console-demo-plugin

cd dynamic-demo-plugin
yarn install
yarn build

2. Run the plugin http server on port 9001

yarn http-server

3. Create the consoleplugin Custom Resource

oc apply -f oc-manifest.yaml

4. Configure the cluster to be no_auth for development purposes

source ./contrib/oc-environment.sh 

5. Run the bridge server

./bin/bridge -plugins=console-demo-plugin=http://localhost:9001 -i18n-namespaces=plugin__console-demo-plugin

6. Visit the following url to see the difference
   http://localhost:9000/k8s/cluster/console.openshift.io~v1~ConsolePlugin/console-demo-plugin/plugin-manifest

Demo

Before

---

After

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.

[Leo6Leo]

/assign @yapei

[yapei]

tested the new added tab functionality

• code editor shows correct plugin manifest content
• copy to clipboard carry content correctly
• download JSON file works well
  no other issues found

/label qe-approved

[openshift-ci-robot]

@Leo6Leo: This pull request references CONSOLE-4690 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 "4.20.0" version, but no target version was set.

In response to this:

Description

Implement the manifest tab for the ConsolePlugin details page using PatternFly 6's CodeEditor component.

The example impacted page path is http://localhost:9000/k8s/cluster/console.openshift.io~v1~ConsolePlugin/console-demo-plugin/plugin-manifest

Steps to test

Prerequisite:
Please make sure you build both front end and backend before proceeding.

1. Build the console-demo-plugin

cd dynamic-demo-plugin
yarn install
yarn build

2. Run the plugin http server on port 9001

yarn http-server

3. Create the consoleplugin Custom Resource

oc apply -f oc-manifest.yaml

4. Configure the cluster to be no_auth for development purposes

source ./contrib/oc-environment.sh 

5. Run the bridge server

./bin/bridge -plugins=console-demo-plugin=http://localhost:9001 -i18n-namespaces=plugin__console-demo-plugin

6. Visit the following url to see the difference
   http://localhost:9000/k8s/cluster/console.openshift.io~v1~ConsolePlugin/console-demo-plugin/plugin-manifest

Demo

Before

---

After

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.

[Leo6Leo]

/retest

[sferich888]

/label px-approved

[openshift-ci-robot]

@Leo6Leo: This pull request references CONSOLE-4690 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 "4.20.0" version, but no target version was set.

In response to this:

Description

Implement the manifest tab for the ConsolePlugin details page using PatternFly 6's CodeEditor component.

The example impacted page path is http://localhost:9000/k8s/cluster/console.openshift.io~v1~ConsolePlugin/console-demo-plugin/plugin-manifest

Steps to test

Prerequisite:
Please make sure you build both front end and backend before proceeding.

1. Build the console-demo-plugin

cd dynamic-demo-plugin
yarn install
yarn build

2. Run the plugin http server on port 9001

yarn http-server

3. Create the consoleplugin Custom Resource

oc apply -f oc-manifest.yaml

4. Configure the cluster to be no_auth for development purposes

source ./contrib/oc-environment.sh 

5. Run the bridge server

./bin/bridge -plugins=console-demo-plugin=http://localhost:9001 -i18n-namespaces=plugin__console-demo-plugin

6. Visit the following url to see the difference
   http://localhost:9000/k8s/cluster/console.openshift.io~v1~ConsolePlugin/console-demo-plugin/plugin-manifest

Demo

Before

---

After

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.

[opayne1]

/label docs-approved

[openshift-ci]

@Leo6Leo: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/okd-scos-e2e-aws-ovn	3cb0661	link	unknown	/test okd-scos-e2e-aws-ovn

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.