-
Notifications
You must be signed in to change notification settings - Fork 613
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OCPBUGS-44800: Add Dynamic Plugins nav item #14521
base: master
Are you sure you want to change the base?
Conversation
rhamilto
commented
Nov 20, 2024
•
edited
Loading
edited
@rhamilto: This pull request references Jira Issue OCPBUGS-44800, which is valid. The bug has been moved to the POST state. 3 validation(s) were run on this bug
Requesting review from QA contact: The bug has been updated to refer to the pull request using the external bug tracker. In response to this: 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. |
24b9421
to
1ec05ea
Compare
We use the label |
/retest |
1 similar comment
/retest |
/test okd-scos-e2e-aws-ovn |
1ec05ea
to
3ac3e7c
Compare
@rhamilto: This pull request references Jira Issue OCPBUGS-44800, which is valid. 3 validation(s) were run on this bug
No GitHub users were found matching the public email listed for the QA contact in Jira ([email protected]), skipping review request. In response to this: 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. |
In the light of a new day, I realized the nav item label should be |
/label acknowledge-critical-fixes-only |
@@ -5,3 +5,4 @@ export const HIDE_USER_WORKLOAD_NOTIFICATIONS_USER_SETTINGS_KEY = | |||
export const FLAG_DEVELOPER_PERSPECTIVE = 'DEVELOPER_PERSPECTIVE'; | |||
export const ACM_PERSPECTIVE_ID = 'acm'; | |||
export const ADMIN_PERSPECTIVE_ID = 'admin'; | |||
export const FLAG_CAN_GET_CONSOLE_OPERATOR_CONFIG = 'FLAG_CAN_GET_CONSOLE_OPERATOR_CONFIG'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
export const FLAG_CAN_GET_CONSOLE_OPERATOR_CONFIG = 'FLAG_CAN_GET_CONSOLE_OPERATOR_CONFIG'; | |
export const FLAG_CAN_GET_CONSOLE_OPERATOR_CONFIG = 'CAN_GET_CONSOLE_OPERATOR_CONFIG'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch, @vojtechszocs. Thanks. Updated.
3ac3e7c
to
16c6473
Compare
/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
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
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 |
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.
I'd update the docs as well to use "Console Plugins." |
I added a story for 4.19. |
3 similar comments
@rhamilto: The following test failed, say
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. |