Tracking issue for supporting drift management. The aim here is to provide insight into what changes occur in the setup of a server instance, e.g. JBAS, and to alert the user to changes they do not expect Basic use cases fall into two categories a) detecting how a server instance changes over time with respect to itself (could also apply to how a group of instances change over time with respect to themselves) b) detecting how a server instance changes over time with respect to a baseline snapshot (could also apply to how a group of instances change over time with respect to a single baseline snapshot) Sample use cases -User wants to be able to see how the configuration of their JBAS instance has changed overtime -User wants to be alerted when their JBAS instance changes configuration -User wants to be able to turn off config detection temporarily, so that they can deploy a new app to the instance without -User wants to be compare a JBAS instance to a specific snapshot
fix blocks/depends bz's
Closing this tracking issue as drift has been implemented for quite some time - this makes no implication about dependencies