-
Notifications
You must be signed in to change notification settings - Fork 50
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
Support all option in rabbitmq_feature_flag module #169
Comments
jovial
added a commit
to jovial/community.rabbitmq
that referenced
this issue
Apr 2, 2024
This is useful to enable all feature flags before an upgrade, see: - https://www.rabbitmq.com/docs/upgrade#enable-required-feature-flags-before-attempting-the-upgrade - https://www.rabbitmq.com/docs/feature-flags#how-to-enable-feature-flags Closes: ansible-collections#169
jovial
added a commit
to jovial/community.rabbitmq
that referenced
this issue
Apr 2, 2024
This is useful to enable all feature flags before an upgrade, see: - https://www.rabbitmq.com/docs/upgrade#enable-required-feature-flags-before-attempting-the-upgrade - https://www.rabbitmq.com/docs/feature-flags#how-to-enable-feature-flags Fixes: ansible-collections#169
I also would like to see this feature in the collection 🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
SUMMARY
Currently you can't do:
As shown here:
https://www.rabbitmq.com/docs/upgrade#enable-required-feature-flags-before-attempting-the-upgrade
Since we check for the current state of the 'all' feature and this comes back as unavailable. It would be nice if we special cased the all feature to not perform this check.
ISSUE TYPE
COMPONENT NAME
rabbitmq_feature_flag module
ADDITIONAL INFORMATION
The text was updated successfully, but these errors were encountered: