-
Notifications
You must be signed in to change notification settings - Fork 659
CONSOLE-4815: 01-Create the feature flag to hide multi-group impersonation feature #15561
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
base: main
Are you sure you want to change the base?
CONSOLE-4815: 01-Create the feature flag to hide multi-group impersonation feature #15561
Conversation
…feature will not be shown to user
…feature will not be shown to user
@Leo6Leo: This pull request references CONSOLE-4815 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 sub-task to target the "4.21.0" version, but no target version was set. 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. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: Leo6Leo The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@Leo6Leo: The following tests 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. |
Description
This PR introduces a feature flag,
bridge/impersonate-enable
, to gate the new multi-group impersonation feature during its development.The multi-group impersonation feature is large and will be split into multiple smaller PRs. This flag will keep the feature hidden from users until all frontend and backend components are complete and merged, ensuring we don't expose an incomplete UI.
The flag is disabled by default. A follow up task to remove the feature flag will be opened when the feature is fully tested and ready for GA.
How this work?
How this will affect the interface you see will be explained in the related PR description.
Note
The number in the PR title specifies the merging order. The larger number means it should be merged after the previous one got merged.
/label tide/merge-method-squash