CONSOLE-4269: add custom ConsolePlugin resource details page #14487

rhamilto · 2024-11-12T21:23:32Z

Includes changes from #14374, which should merge first. Note #14374 includes a bug that needs to be addressed where not Loaded plugins do not appear in the Console plugins list.

In collaboration with @vojtechszocs 🥇

TODOs:

improve Description, Version, Status, Enabled, and CSP Violations popover text | @opayne1, can you help here?

Demos

Plugin is Loaded

Screen.Recording.2024-11-13.at.4.03.13.PM.mov

Plugin is not Loaded (information from pluginStore is not available)

Screen.Recording.2024-11-13.at.4.08.36.PM.mov

Development setup

Build, start, and run the console-demo-plugin locally.
Apply the oc-manifest.yaml to the cluster.
Visit http://localhost:9000/k8s/cluster/console.openshift.io~v1~ConsolePlugin/console-demo-plugin/

openshift-ci-robot · 2024-11-12T21:23:37Z

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

In response to this:

Includes changes from #14374, which should merge first.

In collaboration with @vojtechszocs 🥇

TODOs:

fix failing useTelemetry.spec.ts unit test | @vojtechszocs, mind taking a look?

improve Status, Enabled, and CSP Violations popover text | @opayne1, can you help here?

Screen.Recording.2024-11-12.at.3.52.54.PM.mov

Development setup

Build, start, and run the console-demo-plugin locally.

Apply the oc-manifest.yaml to the cluster.

Visit http://localhost:9000/k8s/cluster/console.openshift.io~v1~ConsolePlugin/console-demo-plugin/

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.

rhamilto · 2024-11-12T21:38:48Z

frontend/packages/console-dynamic-plugin-sdk/src/extensions/details-item.ts

+    /**
+     * An optional description that will appear in the title popover.
+     */
+    description?: string;


Discussed with @TheRealJon. If description isn't supplied, the popover is populated with a description from the resource, which likely doesn't make sense, especially in cases like this where the item isn't in the schema.

openshift-ci-robot · 2024-11-12T21:48:04Z

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

In response to this:

Includes changes from #14374, which should merge first.

In collaboration with @vojtechszocs 🥇

TODOs:

fix failing useTelemetry.spec.ts unit test | @vojtechszocs, mind taking a look?

improve Status, Enabled, and CSP Violations popover text | @opayne1, can you help here?

add Version and Description below Display Name since they're included in the list view? | @jhadvig, WDYT?

Screen.Recording.2024-11-12.at.3.52.54.PM.mov

Development setup

Build, start, and run the console-demo-plugin locally.

Apply the oc-manifest.yaml to the cluster.

Visit http://localhost:9000/k8s/cluster/console.openshift.io~v1~ConsolePlugin/console-demo-plugin/

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-robot · 2024-11-13T18:41:26Z

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

In response to this:

Includes changes from #14374, which should merge first.

In collaboration with @vojtechszocs 🥇

TODOs:

improve Status, Enabled, and CSP Violations popover text | @opayne1, can you help here?

add Version and Description below Display Name since they're included in the list view? | @jhadvig, WDYT?

Screen.Recording.2024-11-12.at.3.52.54.PM.mov

Development setup

Build, start, and run the console-demo-plugin locally.

Apply the oc-manifest.yaml to the cluster.

Visit http://localhost:9000/k8s/cluster/console.openshift.io~v1~ConsolePlugin/console-demo-plugin/

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.

rhamilto · 2024-11-13T18:49:01Z

@vojtechszocs, I removed the changes to useTelemetry.ts from this PR since they are unrelated the scope of the story and opened a bug to address.

rhamilto · 2024-11-13T19:25:30Z

frontend/packages/console-app/src/components/console-operator/ConsoleOperatorConfig.tsx

  const labels = enabled ? t('console-app~Enabled') : t('console-app~Disabled');

  return (
    <>
-      {consoleOperatorConfig && canPatchConsoleOperatorConfig ? (
+      {consoleOperatorConfigLoaded && canPatchConsoleOperatorConfig && !developmentMode ? (


Fixes regression introduced in #14403. We only want to display the button when not in dev mode.

rhamilto · 2024-11-13T19:25:45Z

frontend/packages/console-app/src/components/console-operator/ConsoleOperatorConfig.tsx

@@ -257,15 +279,16 @@ const ConsolePluginsTable: React.FC<ConsolePluginsTableProps> = ({ obj, rows, lo
              ({ name, version, description, status, enabled, errorMessage, hasCSPViolations }) => (
                <Tr key={name}>
                  <Td dataLabel={columns[0].id}>
-                    <ResourceLink groupVersionKind={consolePluginGVK} name={name} hideIcon />
+                    {!developmentMode ? (


Fixes regression introduced in #14403. We only want to display the link when not in dev mode.

opayne1

Made a few tweaks. Let me know your thoughts.

opayne1 · 2024-11-13T19:07:04Z

frontend/packages/console-app/locales/en/console-app.json

+  "Status": "Status",
+  "The state of the plugin.": "The state of the plugin.",
+  "Enabled": "Enabled",
+  "A boolean to determine whether or not the plugin renders in console.": "A boolean to determine whether or not the plugin renders in console.",


What about shortening it? I think the "whether or not" is implied.

Suggested change

"A boolean to determine whether or not the plugin renders in console.": "A boolean to determine whether or not the plugin renders in console.",

"A boolean to determine if the plugin renders in console.": "A boolean to determine if the plugin renders in console.",

Sorry, @opayne1. I rewrote this while making some additions and just noticed your comment. The text now reads, Whether or not the plugin renders in console.. WDYT?

opayne1 · 2024-11-13T19:09:08Z

frontend/packages/console-app/locales/en/console-app.json

+  "Enabled": "Enabled",
+  "A boolean to determine whether or not the plugin renders in console.": "A boolean to determine whether or not the plugin renders in console.",
+  "CSP Violations": "CSP Violations",
+  "Plugin might have violated the Console Content Security Policy.": "Plugin might have violated the Console Content Security Policy.",


Should this one be similar to the one on line 235? or can we make it a complete sentence/

Suggested change

"Plugin might have violated the Console Content Security Policy.": "Plugin might have violated the Console Content Security Policy.",

"This plugin might have violated the Console Content Security Policy.": "This plugin might have violated the Console Content Security Policy.",

Sorry, @opayne1. I rewrote this while making some additions and just noticed your comment. The text now reads, Whether or not the plugin might have violated the Console Content Security Policy.. WDYT?

openshift-ci-robot · 2024-11-13T21:04:46Z

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

In response to this:

Includes changes from #14374, which should merge first.

In collaboration with @vojtechszocs 🥇

TODOs:

improve Status, Enabled, and CSP Violations popover text | @opayne1, can you help here?

add Version and Description below Display Name since they're included in the list view? | @jhadvig, WDYT?

Screen.Recording.2024-11-12.at.3.52.54.PM.mov

Development setup

Build, start, and run the console-demo-plugin locally.

Apply the oc-manifest.yaml to the cluster.

Visit http://localhost:9000/k8s/cluster/console.openshift.io~v1~ConsolePlugin/console-demo-plugin/

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-robot · 2024-11-13T21:07:08Z

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

In response to this:

Includes changes from #14374, which should merge first.

In collaboration with @vojtechszocs 🥇

TODOs:

improve Description, Version, Status, Enabled, and CSP Violations popover text | @opayne1, can you help here?

add Version and Description below Display Name since they're included in the list view? | @jhadvig, WDYT?

Demos

Plugin is Loaded

Screen.Recording.2024-11-13.at.4.03.13.PM.mov

Plugin is not Loaded (information from pluginStore is not available)

Screen.Recording.2024-11-13.at.4.04.05.PM.mov

Development setup

Build, start, and run the console-demo-plugin locally.

Apply the oc-manifest.yaml to the cluster.

Visit http://localhost:9000/k8s/cluster/console.openshift.io~v1~ConsolePlugin/console-demo-plugin/

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-robot · 2024-11-13T21:07:42Z

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

In response to this:

Includes changes from #14374, which should merge first.

In collaboration with @vojtechszocs 🥇

TODOs:

improve Description, Version, Status, Enabled, and CSP Violations popover text | @opayne1, can you help here?

Demos

Plugin is Loaded

Screen.Recording.2024-11-13.at.4.03.13.PM.mov

Plugin is not Loaded (information from pluginStore is not available)

Screen.Recording.2024-11-13.at.4.04.05.PM.mov

Development setup

Build, start, and run the console-demo-plugin locally.

Apply the oc-manifest.yaml to the cluster.

Visit http://localhost:9000/k8s/cluster/console.openshift.io~v1~ConsolePlugin/console-demo-plugin/

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-robot · 2024-11-13T21:10:19Z

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

In response to this:

Includes changes from #14374, which should merge first.

In collaboration with @vojtechszocs 🥇

TODOs:

improve Description, Version, Status, Enabled, and CSP Violations popover text | @opayne1, can you help here?

Demos

Plugin is Loaded

Screen.Recording.2024-11-13.at.4.03.13.PM.mov

Plugin is not Loaded (information from pluginStore is not available)

Screen.Recording.2024-11-13.at.4.08.36.PM.mov

Development setup

Build, start, and run the console-demo-plugin locally.

Apply the oc-manifest.yaml to the cluster.

Visit http://localhost:9000/k8s/cluster/console.openshift.io~v1~ConsolePlugin/console-demo-plugin/

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-robot · 2024-11-13T21:10:43Z

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

In response to this:

Includes changes from #14374, which should merge first.

In collaboration with @vojtechszocs 🥇

TODOs:

improve Description, Version, Status, Enabled, and CSP Violations popover text | @opayne1, can you help here?

Demos

Plugin is Loaded

Screen.Recording.2024-11-13.at.4.03.13.PM.mov

Plugin is not Loaded (information from pluginStore is not available)

Screen.Recording.2024-11-13.at.4.08.36.PM.mov

Development setup

Build, start, and run the console-demo-plugin locally.

Apply the oc-manifest.yaml to the cluster.

Visit http://localhost:9000/k8s/cluster/console.openshift.io~v1~ConsolePlugin/console-demo-plugin/

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-robot · 2024-11-13T21:37:05Z

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

In response to this:

Includes changes from #14374, which should merge first. Note #14374 includes a bug that needs to be addressed where not Loaded plugins do not appear in the Console plugins list.

In collaboration with @vojtechszocs 🥇

TODOs:

improve Description, Version, Status, Enabled, and CSP Violations popover text | @opayne1, can you help here?

Demos

Plugin is Loaded

Screen.Recording.2024-11-13.at.4.03.13.PM.mov

Plugin is not Loaded (information from pluginStore is not available)

Screen.Recording.2024-11-13.at.4.08.36.PM.mov

Development setup

Build, start, and run the console-demo-plugin locally.

Apply the oc-manifest.yaml to the cluster.

Visit http://localhost:9000/k8s/cluster/console.openshift.io~v1~ConsolePlugin/console-demo-plugin/

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.

jhadvig · 2024-11-14T22:10:03Z

QE Approver:
/assign @yapei
Docs Approver:
/assign @opayne1
PX Approver:
/assign @reestr

Also worth to notice that this PR is cherry-picking CONSOLE-4264: Notify users of Console plugin related Content Security Policy violations and also contributing a fix for issue found by @yapei.

@opayne1 please review only commits contributed by @rhamilto, since @vojtechszocs was already reviewed by you.
@yapei please test only functionality related to the ConsolePlugin details page.
Thank you 🥇

rhamilto · 2024-11-15T02:10:44Z

/test e2e-gcp-console

reestr · 2024-11-15T08:19:55Z

/label px-approved

yanpzhan · 2024-11-15T08:43:01Z

Checked on cluster launched against the pr, tested consoleplugin 'Details' page and 'Plugin manifest' tab, features work as expected.
/label qe-approved

openshift-ci-robot · 2024-11-15T08:43:08Z

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

In response to this:

Includes changes from #14374, which should merge first. Note #14374 includes a bug that needs to be addressed where not Loaded plugins do not appear in the Console plugins list.

In collaboration with @vojtechszocs 🥇

TODOs:

improve Description, Version, Status, Enabled, and CSP Violations popover text | @opayne1, can you help here?

Demos

Plugin is Loaded

Screen.Recording.2024-11-13.at.4.03.13.PM.mov

Plugin is not Loaded (information from pluginStore is not available)

Screen.Recording.2024-11-13.at.4.08.36.PM.mov

Development setup

Build, start, and run the console-demo-plugin locally.

Apply the oc-manifest.yaml to the cluster.

Visit http://localhost:9000/k8s/cluster/console.openshift.io~v1~ConsolePlugin/console-demo-plugin/

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.

ahardin-rh · 2024-11-15T14:09:54Z

/label docs-approved

jhadvig · 2024-11-15T14:58:47Z

/lgtm

openshift-ci · 2024-11-15T14:59:09Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jhadvig, rhamilto

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~~ [jhadvig,rhamilto]

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

spadgett · 2024-11-15T15:55:18Z

Hey, @rhamilto. This is great. I'm happy to see we have a nice details page.

Out of scope for this PR and story, but I had a few thoughts for future improvements:

It would be good to show the plugin's supported OCP versions and make it clear when a plugin is disabled since its version range doesn't match the current OCP version. (I believe the supported versions are in the manifest, but would be good to have this on the overview tab. See plugin manifest properties.)
Should we add a top-level nav items for Console Plugins to the Administration nav section? It would make it more discoverable.
Syntax highlighting for the manifest JSON would be nice. Maybe we can use Monaco.
I think a table of the extensions used by the plugin would be nice to have in addition to the manifest JSON (but keep the manifest tab for the complete JSON).

@jhadvig @vojtechszocs FYI

rhamilto · 2024-11-15T16:24:41Z

Hey, @rhamilto. This is great. I'm happy to see we have a nice details page.

Thanks for the feedback, @spadgett.

It would be good to show the plugin's supported OCP versions and make it clear when a plugin is disabled since its version range doesn't match the current OCP version. (I believe the supported versions are in the manifest, but would be good to have this on the overview tab. See plugin manifest properties.)

Easy enough to add.

Should we add a top-level nav items for Console Plugins to the Administration nav section? It would make it more discoverable.

Agreed.

Syntax highlighting for the manifest JSON would be nice. Maybe we can use Monaco.

@vojtechszocs and I started down the path of using Monaco, but decided against it for the initial implementation because the read only mode of the existing YAML editor posed some usability questions that we didn't have time to contend with.

I think a table of the extensions used by the plugin would be nice to have in addition to the manifest JSON (but keep the manifest tab for the complete JSON).

Easy enough to add.

rhamilto · 2024-11-19T14:11:59Z

It would be good to show the plugin's supported OCP versions and make it clear when a plugin is disabled since its version range doesn't match the current OCP version. (I believe the supported versions are in the manifest, but would be good to have this on the overview tab. See plugin manifest properties.)

@spadgett, maybe something like this (note all the details in the video are not accurate such as Enabled)?

Screen.Recording.2024-11-19.at.9.08.21.AM.mov

rhamilto · 2024-11-19T16:42:52Z

3. Syntax highlighting for the manifest JSON would be nice. Maybe we can use Monaco.

@spadgett, we must've done something wonky with our initial attempt as this appears to be working correctly now.

I do wonder, is it weird to have two YAML editors?

Screen.Recording.2024-11-19.at.2.52.36.PM.mov

rhamilto · 2024-11-19T19:24:15Z

4. I think a table of the extensions used by the plugin would be nice to have in addition to the manifest JSON (but keep the manifest tab for the complete JSON).

Hmm. Given the variance amongst the extension properties, this one is a bit trickier to tabularize. 🤔

spadgett · 2024-11-19T20:51:02Z

It would be good to show the plugin's supported OCP versions and make it clear when a plugin is disabled since its version range doesn't match the current OCP version. (I believe the supported versions are in the manifest, but would be good to have this on the overview tab. See plugin manifest properties.)

@spadgett, maybe something like this (note all the details in the video are not accurate such as Enabled)?

Screen.Recording.2024-11-19.at.9.08.21.AM.mov

@rhamilto Yeah, that looks good. We should probably show the current console version in the warning popover and add something to the plugin list table if we don't already have it. We can make it a separate story.

spadgett · 2024-11-19T20:54:11Z

I think a table of the extensions used by the plugin would be nice to have in addition to the manifest JSON (but keep the manifest tab for the complete JSON).

Hmm. Given the variance amongst the extension properties, this one is a bit trickier to tabularize. 🤔

Yeah, I was hesitant about that, too. But even just the list of extension IDs would be helpful. We could show the resource kind for any extension that targets a specific resource and leave the column blank for other extension points. Or maybe not a table, but some other presentation.

spadgett · 2024-11-19T20:58:28Z

Syntax highlighting for the manifest JSON would be nice. Maybe we can use Monaco.

@spadgett, we must've done something wonky with our initial attempt as this appears to be working correctly now.

I do wonder, is it weird to have two YAML editors?

Yeah, I'm undecided. Maybe we can style it differently or simplify the editor to make it more clear that it's read-only?

All of these suggestions can be follow-up PRs, particularly since this has merged. I'd say the compatible versions tweak is the most important to help admins troubleshoot plugins that aren't enabled.

rhamilto · 2024-11-20T14:47:34Z

2. Should we add a top-level nav items for Console Plugins to the Administration nav section? It would make it more discoverable.

Made this a bug so we can backport: #14521 @spadgett, mind reviewing?

This reverts commit 3f37ea0, reversing changes made to 3953d93.

Notify users of plugin related Content Security Policy violations

d054036

openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Nov 12, 2024

openshift-ci bot requested review from cyril-ui-developer and spadgett November 12, 2024 21:23

openshift-ci bot added component/core Related to console core functionality component/olm Related to OLM approved Indicates a PR has been approved by an approver from all required OWNERS files. component/sdk Related to console-plugin-sdk labels Nov 12, 2024

rhamilto changed the title ~~CONSOLE-4269: add custom ConsolePlugin resource details page~~ [WIP] CONSOLE-4269: add custom ConsolePlugin resource details page Nov 12, 2024

openshift-ci bot added component/shared Related to console-shared kind/i18n Indicates issue or PR relates to internationalization or has content that needs to be translated do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. labels Nov 12, 2024

rhamilto commented Nov 12, 2024

View reviewed changes

rhamilto force-pushed the CONSOLE-4269 branch 2 times, most recently from ce82a9b to be219d6 Compare November 13, 2024 18:40

rhamilto commented Nov 13, 2024

View reviewed changes

opayne1 reviewed Nov 13, 2024

View reviewed changes

CONSOLE-4269: add custom ConsolePlugin resource details page

505389d

rhamilto force-pushed the CONSOLE-4269 branch from be219d6 to 505389d Compare November 13, 2024 21:04

jhadvig changed the title ~~[WIP] CONSOLE-4269: add custom ConsolePlugin resource details page~~ CONSOLE-4269: add custom ConsolePlugin resource details page Nov 14, 2024

openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Nov 14, 2024

openshift-ci bot added the px-approved Signifies that Product Support has signed off on this PR label Nov 15, 2024

openshift-ci bot added the qe-approved Signifies that QE has signed off on this PR label Nov 15, 2024

Fix for openshift#14374

833d56b

rhamilto force-pushed the CONSOLE-4269 branch from a44b25e to 833d56b Compare November 15, 2024 13:24

openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Nov 15, 2024

openshift-ci bot added the docs-approved Signifies that Docs has signed off on this PR label Nov 15, 2024

openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Nov 15, 2024

openshift-merge-bot bot merged commit 3f37ea0 into openshift:master Nov 15, 2024
6 of 7 checks passed

rhamilto deleted the CONSOLE-4269 branch November 15, 2024 23:45

rhamilto mentioned this pull request Nov 15, 2024

CONSOLE-4268: add CSP violations to cluster dashboard #14475

Merged

logonoff added a commit to logonoff/openshift-console that referenced this pull request Nov 26, 2024

Revert "Merge pull request openshift#14487 from rhamilto/CONSOLE-4269"

469cafc

This reverts commit 3f37ea0, reversing changes made to 3953d93.

	"A boolean to determine whether or not the plugin renders in console.": "A boolean to determine whether or not the plugin renders in console.",
	"A boolean to determine if the plugin renders in console.": "A boolean to determine if the plugin renders in console.",

	"Plugin might have violated the Console Content Security Policy.": "Plugin might have violated the Console Content Security Policy.",
	"This plugin might have violated the Console Content Security Policy.": "This plugin might have violated the Console Content Security Policy.",

CONSOLE-4269: add custom ConsolePlugin resource details page #14487

CONSOLE-4269: add custom ConsolePlugin resource details page #14487

Conversation

rhamilto commented Nov 12, 2024 • edited Loading

Demos

Development setup

openshift-ci-robot commented Nov 12, 2024 • edited by openshift-ci bot Loading

Development setup

rhamilto Nov 12, 2024

Choose a reason for hiding this comment

openshift-ci-robot commented Nov 12, 2024 • edited by openshift-ci bot Loading

Development setup

openshift-ci-robot commented Nov 13, 2024 • edited by openshift-ci bot Loading

Development setup

rhamilto commented Nov 13, 2024

rhamilto Nov 13, 2024

Choose a reason for hiding this comment

rhamilto Nov 13, 2024

Choose a reason for hiding this comment

opayne1 left a comment

Choose a reason for hiding this comment

opayne1 Nov 13, 2024

Choose a reason for hiding this comment

rhamilto Nov 13, 2024

Choose a reason for hiding this comment

opayne1 Nov 13, 2024

Choose a reason for hiding this comment

rhamilto Nov 13, 2024

Choose a reason for hiding this comment

openshift-ci-robot commented Nov 13, 2024 • edited by openshift-ci bot Loading

Development setup

openshift-ci-robot commented Nov 13, 2024 • edited by openshift-ci bot Loading

Demos

Development setup

openshift-ci-robot commented Nov 13, 2024 • edited by openshift-ci bot Loading

Demos

Development setup

openshift-ci-robot commented Nov 13, 2024 • edited by openshift-ci bot Loading

Demos

Development setup

openshift-ci-robot commented Nov 13, 2024 • edited by openshift-ci bot Loading

Demos

Development setup

openshift-ci-robot commented Nov 13, 2024 • edited by openshift-ci bot Loading

Demos

Development setup

jhadvig commented Nov 14, 2024 • edited Loading

rhamilto commented Nov 15, 2024

reestr commented Nov 15, 2024

yanpzhan commented Nov 15, 2024

openshift-ci-robot commented Nov 15, 2024 • edited by openshift-ci bot Loading

Demos

Development setup

ahardin-rh commented Nov 15, 2024

jhadvig commented Nov 15, 2024

openshift-ci bot commented Nov 15, 2024

spadgett commented Nov 15, 2024

rhamilto commented Nov 15, 2024

rhamilto commented Nov 19, 2024 • edited Loading

rhamilto commented Nov 19, 2024 • edited Loading

rhamilto commented Nov 19, 2024 • edited Loading

spadgett commented Nov 19, 2024

spadgett commented Nov 19, 2024

spadgett commented Nov 19, 2024

rhamilto commented Nov 20, 2024

rhamilto commented Nov 12, 2024 •

edited

Loading

openshift-ci-robot commented Nov 12, 2024 •

edited by openshift-ci bot

Loading

openshift-ci-robot commented Nov 12, 2024 •

edited by openshift-ci bot

Loading

openshift-ci-robot commented Nov 13, 2024 •

edited by openshift-ci bot

Loading

openshift-ci-robot commented Nov 13, 2024 •

edited by openshift-ci bot

Loading

openshift-ci-robot commented Nov 13, 2024 •

edited by openshift-ci bot

Loading

openshift-ci-robot commented Nov 13, 2024 •

edited by openshift-ci bot

Loading

openshift-ci-robot commented Nov 13, 2024 •

edited by openshift-ci bot

Loading

openshift-ci-robot commented Nov 13, 2024 •

edited by openshift-ci bot

Loading

openshift-ci-robot commented Nov 13, 2024 •

edited by openshift-ci bot

Loading

jhadvig commented Nov 14, 2024 •

edited

Loading

openshift-ci-robot commented Nov 15, 2024 •

edited by openshift-ci bot

Loading

rhamilto commented Nov 19, 2024 •

edited

Loading

rhamilto commented Nov 19, 2024 •

edited

Loading

rhamilto commented Nov 19, 2024 •

edited

Loading