Skip to content
Discussion options

You must be logged in to vote

This is not a bug.

Definition imports can involve a non-trivial web of inter-dependencies between different resources. Perhaps the most famous scenario is a shovel that needs a source and a destination defined (up until #11793, and to a certain extent, 3.8.6).

They may or may not be defined in the definitions, or before the definitions. Definition import has been moved to the latest possible moment more than once in RabbitMQ's history, and it's never enough.

The solution is to untangle the core of your topology (virtual hosts, queues, streams, bindings, users, permissions) and everything that depends on that topology. The core can be imported at node boot, everything else has to be import…

Replies: 3 comments 1 reply

Comment options

You must be logged in to vote
0 replies
Answer selected by PaperTsar
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
1 reply
@michaelklishin
Comment options

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
3 participants
Converted from issue

This discussion was converted from issue #14774 on October 22, 2025 02:14.