seanshahkarami
commented
6 years ago I'm thinking this may be better to get the config right and then snapshot that to seed future deployments. It can be updated, it's just unlikely to change very often. In light of this, I'm closing this issue.
RabbitMQ is able to save / restore it's current configuration state. This includes all internal configurations regarding exchanges, queues, bindings, users, permissions, virtual hosts, etc... We should probably have this backed up automatically and saved in case we ever need to restore the state of the broker. In particular, once we get to the point of having distinct users for each node, this will ensure we already have a backup plan in place for those credentials.