Hi,
Sorry if this has been asked before, but I did a search and didn't see an answer.
I'm trying to automate the setup of the rabbitmq configurations. I was wondering if there were any technical reasons not to configure shovels dynamically vs static config files.
Are both of them equally dependable? As in the configurations are persistent through random system/service down events etc.
As I understand the settings get stored inside a db anyway so I'm not sure if static config files are necessary for making sure configurations are persistent.
The only thing I see is maybe if the rabbitctl reset was issued then the dynamic settings get wiped out, whereas the static config file remains.
Right now I'm automating the shovel configs by using commands to do the dynamic configurations for the shovels. I could wipe out the system and run the automation script and it would recreate the cluster using a generated config file and then the shovels dynamically through "rabbitctl set_parameter shovel <param> <param>".
Anyway, my question is can I assume that the dynamic configurations are just as persistent as configs coming from a config file?
What's the difference between a static shovel vs a dynamic shovel besides the fact that one came from a static config file and the other through rabbitctl commands?
Thanks,
Kin L