BundleWorks allows you to track all changes to configuration throughout your environments. It accomplishes this using an attribute named 'Runtime-Config' within a bundle info file and a set configuration management commands.

BundleWorks looks for configuration changes in a deployment during the execution of the start and run commands. BundleWorks will read any paths from the attribute 'Runtime-Config' inside the bundle info file and check these locations to see if configuration has changed since the last check. If a change is detected, that configuration file is versioned inside the BundleWorks work directory.

BundleWorks also provides an explicit check_config function which can be used to trigger a configuration check within a deployment.

For each configuration file, changes are stored as revisions. Each revision is assigned a number, starting at 1 and incrementing each time a configuration change is saved. This revision number can be used to view and restore prior versions of a configuration file.

BundleWorks provides a set of four commands to work with versioned configuration:

The reference section provides more detail for each of these commands. The tutorial shows all of these commands in action.