Github user mtaylor commented on the issue:
https://github.com/apache/activemq-artemis/pull/1345
Having this policy driven seems to be the way to satisfy both requirements.
It also still makes sense if we do go down the route of storing
queues/addresses in config only (although as @michaelandrepearce mentioned this
will likely be an API break anyway).
@andytaylor @michaelandrepearce I don't think we need to implement all
policies right away, this can be user driven as and when requirements crop up.
The simplest thing right now IMO is just to amend this commit to use something
like:
configDeleteQueue=[Off (Default), Force].
And ensure the consequences of "Force" are clearly documented.
@michaelandrepearce Given this is to become policy driven I can see more of
a requirement for this to be set at the address-settings level.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
