Github user mtaylor commented on the issue:
https://github.com/apache/activemq-artemis/pull/1345
@michaelandrepearce Sure. I get the configuration management tool use case.
Two comments:
1. Does it make sense to enable this at the address-settings level vs just
a global wide param?
2. If this is switched on, do we want to disable other means of managing
addresses?
We have discussed in the past, making the XML configuration the single
source of truth for queues and addresses. I think the original reason for not
supporting address/queue deletes via configuration was to avoid message loss.
In this scenario, I think dropping a queue with messages is appropriate. We
just need to make that clear in the documentation.
This topic has cropped up in the past, do you guys have any input?
@andytaylor @clebertsuconic @jbertram.
On the PR. It looks good, I did a few extra manual tests with wildcard
addresses, it works as expected
Thanks
---
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.
---
