[MXS-1297] Save current configuration to a file Created: 2017-06-26 Updated: 2017-09-22 Resolved: 2017-09-22 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | Core |
| Affects Version/s: | 2.2.0 |
| Fix Version/s: | 2.2.0 |
| Type: | Task | Priority: | Minor |
| Reporter: | Esa Korhonen | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Sprint: | 2017-38, 2017-39 |
| Description |
|
MaxScale reads configuration files from several locations when starting. In addition to the main file, there may be separate files for different configuration units. Also, runtime config changes are saved to their own files. For clarity, there should be an option to save the total resulting configuration to a file, which could then be used as the main file. This might also be useful for syncing runtime changes to other MaxScales. |
| Comments |
| Comment by Johan Wikman [ 2017-06-28 ] |
|
If the content of the file is created from the resulting runtime configuration, then the output will not contain any comments that there originally might have been (in the static file). The generated file could not as such be used for syncing runtime changes to other MaxScale's, as that then would mean that the configuration file structure on different MaxScales would not be identical. Unless the resulting file would be taken into use everywhere, in which case the dynamic files must be deleted. |