activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (ARTEMIS-1235) Support the ability to enable queue and address deletion when broker.xml changes
Date Sat, 17 Jun 2017 18:52:02 GMT


ASF GitHub Bot commented on ARTEMIS-1235:

Github user michaelandrepearce commented on the issue:
    Re configuring outside the config, this is indeed the wanted behaviour that if by enabling
then config is the true source.
    The use case is to manage environments/systems via tools like puppet/chef.
    When using puppet or chef, you don't want people changing the state of the environment
/ system, as such if someone (even an admin) changed via an admin console or cli, that change
should be regressed, this is indeed the reasons for using such tools as even manage linux
level stuff via it to ensure linux configure and state, as environment / system change should
go via puppet / chef, this makes environments repeatable, also make change management easier
having only single process.

> Support the ability to enable queue and address deletion when broker.xml changes
> --------------------------------------------------------------------------------
>                 Key: ARTEMIS-1235
>                 URL:
>             Project: ActiveMQ Artemis
>          Issue Type: New Feature
>            Reporter: Michael Andre Pearce
> Currently on config reload, as per:
> Once the configuration file is changed (broker.xml) the following modules will be reloaded
> Address Settings
> Security Settings
> Diverts
> Addresses & queues
> Notice: Address & queues won't be removed upon reload, given the risk of losing messages.
You may execute explicit CLI or Management operations to remove destinations.
> Where an organisation uses tools like puppet or chef and need to fully change manage
the broker they need an ability to delete queues and topics also via the config, as these
tools control state of systems by config. Like wise in these scenario's where such tools are
used to control state of a system typically an organisation will have controls and pre-prod
environments where they push config through the environments as such risk of issue is removed
re data loss / or accepted risk, as would have been pre-validated in non-ciritical non-prod
> The default behaviour should be as is today (e.g. delete still doesn't occur), but an
optional toggle so that queue's and address's are sync'd removed inline with the broker xml.

> Ideally it should be possible to toggle this ability by address pattern so if some address's
you don't wish controlled this way and others you do, this should be possible.

This message was sent by Atlassian JIRA

View raw message