Open rhamilto opened 2 days ago
@rhamilto: This pull request references Jira Issue OCPBUGS-44800, which is valid. The bug has been moved to the POST state.
Requesting review from QA contact: /cc @yapei
The bug has been updated to refer to the pull request using the external bug tracker.
We use the label Dynamic plugins
in the Overview and the About modal (screenshots below), but I think Console Plugins
is the proper choice for the nav item since that aligns with the tab label, but it is odd we have this discrepancy. Maybe we need to revisit? @jhadvig, @spadgett, @vojtechszocs, WDYT?
/retest
/retest
/test okd-scos-e2e-aws-ovn
@rhamilto: This pull request references Jira Issue OCPBUGS-44800, which is valid.
No GitHub users were found matching the public email listed for the QA contact in Jira (yapei@redhat.com), skipping review request.
We use the label
Dynamic plugins
in the Overview and the About modal (screenshots below), but I thinkConsole Plugins
is the proper choice for the nav item since that aligns with the tab label, but it is odd we have this discrepancy. Maybe we need to revisit? @jhadvig, @spadgett, @vojtechszocs, WDYT?
In the light of a new day, I realized the nav item label should be Dynamic Plugins
, so I've updated this PR.
/label acknowledge-critical-fixes-only
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: rhamilto, vojtechszocs
The full list of commands accepted by this bot can be found here.
The pull request process is described here
We use the label
Dynamic plugins
in the Overview and the About modal (screenshots below), but I thinkConsole Plugins
is the proper choice for the nav item since that aligns with the tab label, but it is odd we have this discrepancy. Maybe we need to revisit? @jhadvig, @spadgett, @vojtechszocs, WDYT?
IMO it should be "Console Plugins" everywhere. That's the only kind of plugin we've ever had an external API for. "Static plugins" were always an internal thing, so there's not a need to differentiate between them for users. I think putting "Dynamic" in the label raises more questions than it answers for most users. Also "Console Plugin" matches the CRD kind.
We use the label
Dynamic plugins
in the Overview and the About modal (screenshots below), but I thinkConsole Plugins
is the proper choice for the nav item since that aligns with the tab label, but it is odd we have this discrepancy. Maybe we need to revisit? @jhadvig, @spadgett, @vojtechszocs, WDYT?IMO it should be "Console Plugins" everywhere. That's the only kind of plugin we've ever had an external API for. "Static plugins" were always an internal thing, so there's not a need to differentiate between them for users. I think putting "Dynamic" in the label raises more questions than it answers for most users. Also "Console Plugin" matches the CRD kind.
IIRC, we went with Dynamic Plugins so as not to conflate the functionality with the resource. One could argue that subtlety is lost on users however...
Docs uses "Dynamic Plugins": https://docs.openshift.com/container-platform/4.17/web_console/dynamic-plugin/overview-dynamic-plugin.html
IIRC, we went with Dynamic Plugins so as not to conflate the functionality with the resource. One could argue that subtlety is lost on users however...
To me, this could create more confusion because it sounds like they're two different things. There are also other kinds of plugins on the platform (for instance, network plugins or CLI plugins). The most important differentiator is that it's a console plugin.
Docs uses "Dynamic Plugins": https://docs.openshift.com/container-platform/4.17/web_console/dynamic-plugin/overview-dynamic-plugin.html
I'd update the docs as well to use "Console Plugins."
I added a story for 4.19.
/retest-required
Remaining retests: 0 against base HEAD ea76ee699113d251e74be989e6ca9613e717db33 and 2 for PR HEAD 16c6473bd04889d230ee2d25320a98ce66707129 in total
@rhamilto: 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/e2e-gcp-console | 16c6473bd04889d230ee2d25320a98ce66707129 | link | true | /test e2e-gcp-console |
Full PR test history. Your PR dashboard.
/retest-required
Remaining retests: 0 against base HEAD d87887934af62b7306ab458208b0002c009aa40c and 1 for PR HEAD 16c6473bd04889d230ee2d25320a98ce66707129 in total