Currently the queue configuration is applied when a service starts up. This is not idea for a couple of reasons
It means the service needs to run at elevated permissions
All instances apply the configuration at startup
Because of point 2, unsubscriptions from topics can't be done as neither old nor new service will know which is the current configuration
This feature should add a cli option that applies the current configuration and remove any redundant topic/queue subscriptions (the latter should be possible to be disabled via additional flags). This will allow migrations to fit in as part of a broader CI/CD process.
Currently the queue configuration is applied when a service starts up. This is not idea for a couple of reasons
This feature should add a cli option that applies the current configuration and remove any redundant topic/queue subscriptions (the latter should be possible to be disabled via additional flags). This will allow migrations to fit in as part of a broader CI/CD process.