Return non-0 exit code when failing to enable an experimental feature flag (backport #12066) #12067
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a follow-up to #11998. The main change is to return a non-zero exit code for
rabbitmqctl enable_feature_flag <expermental-flag>
. When enablingkhepri_db
locally I wasn't 100% surerabbitmqctl
didn't attempt to enable the flag regardless (i.e. the message seemed more like a warning) and I thought a non-zero exit code and the error text would make it more obvious.Also included are a typo fix and unit tests for the
--experimental
flag, one forall
and another for a given experimental feature flag name.This is an automatic backport of pull request #12066 done by Mergify.