Optionally persisting topology (queues, topics and subscriptions)

[glenjamin]

Optionally persisting topology (queues, topics and subscriptions)

[Admiral-Piett]

@glenjamin Hm, interesting idea. Have you had any luck with just making your changes in a config file and pointing your goaws instance at that? If not, what's missing from that, that you need to see other than you having to make it yourself? That's really the only persistance we have immediately handy.

Though, I could see value in a sort of - "export my state" command into a config file, I'd want to chew on that a bit.

Let me know about the config option. Thanks for thinking it through though!

[glenjamin]

The main thing I'm hoping to avoid is having to repeat our topology config in multiple places, as that runs the risk of it going out of sync

[Admiral-Piett]

Hm, interesting. The only way we currently have to persist a particular setup is through a config file - which I what I would recommend to you in the meantime, event though, you would have to maintain both things you're right. I can see that exporting a current config as being beneficial, though I'll have to think through a design for it. We can leave it here for now.