This repository has been archived by the owner on Nov 17, 2020. It is now read-only.
Respect management.load_definitions for backwards compatibility #818
Comments
michaelklishin
added a commit
that referenced
this issue
Jun 9, 2020
Previously we tried to rely on rabbitmq_management env being loaded in the core. That is suboptimal and has unintentional side effects. References #2368, #2373. Closes #818.
michaelklishin
added a commit
that referenced
this issue
Jun 9, 2020
Previously we tried to rely on rabbitmq_management env being loaded in the core. That is suboptimal and has unintentional side effects. References rabbitmq/rabbitmq-management#2368, rabbitmq/rabbitmq-management#2373. Closes #818.
michaelklishin
added a commit
that referenced
this issue
Jun 9, 2020
Previously we tried to rely on rabbitmq_management env being loaded in the core. That is suboptimal and has unintentional side effects. References rabbitmq/rabbitmq-management#2368, rabbitmq/rabbitmq-management#2373. Closes #818.
michaelklishin
added a commit
to rabbitmq/rabbitmq-server
that referenced
this issue
Jun 9, 2020
References #2368, #2373, rabbitmq/rabbitmq-management#818. (cherry picked from commit df1fffb)
michaelklishin
added a commit
to rabbitmq/rabbitmq-server
that referenced
this issue
Jun 9, 2020
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Ever since definition load on boot has moved into the core,
management.load_definitionsis unintentionally ignored. Instead of trying to work around this in the core we should do it in this plugin, e.g. with an additional boot step.The text was updated successfully, but these errors were encountered: