Skip to content
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

Make it hard to accidentally enable an experimental feature flag (backport #11998) #12058

Merged
merged 5 commits into from
Aug 19, 2024

Conversation

mergify[bot]
Copy link

@mergify mergify bot commented Aug 19, 2024

Currently it's easy to enable an experimental feature flag like khepri_db by accident. Given the operation is irreversible, this leads to serious consequences when done in a production environment.

This PR implements the following changes:

  • Management UI
    • Split the feature flags page into two tables - first with all but experimental feature flags, the second with only the experimental flags (and a warning)
    • To enable an experimental feature flag, a checkbox needs to be toggled first
  • CLI
    • rabbitmqctl enable_feature_flag khepri_db won't work unless a new flag --experimental is provided
Screenshot 2024-08-14 at 12 19 57
This is an automatic backport of pull request #11998 done by [Mergify](https://mergify.com).

Plus, a slightly more scary error message

(cherry picked from commit e3302f2)
Also, remove the `undef` case which was only needed for
RabbitMQ 3.7 and older.

(cherry picked from commit ddb117f)
(cherry picked from commit 396ad7a)
@michaelklishin michaelklishin merged commit d5cf986 into v4.0.x Aug 19, 2024
197 checks passed
@michaelklishin michaelklishin deleted the mergify/bp/v4.0.x/pr-11998 branch August 19, 2024 21:01
michaelklishin added a commit that referenced this pull request Aug 19, 2024
Make it hard to accidentally enable an experimental feature flag (backport #11998) (backport #12058)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants