I attempted to use this formula to install v0.9.4.1 and encountered a few different errors associated with breaking config file changes introduced in v0.9.0+:
In v0.9.0, a new [meta]section was added to store clustering metadata. The current config template for 0.9 breaks with this error:
run: Meta.Dir must be specified. To generate a valid configuration file run `influxd config > influxdb.generated.conf`.
Other changes have been introduced in minor versions like v0.9.3 that break how certain configurations sections are parsed, resulting in errors like this:
run: parse config: Type mismatch for 'run.Config.udp': Expected slice but found 'map[string]interface {}'.
I'd like to be able to help adjust the formula config files for some of these updates, but I'm not sure what pattern is recommended to accommodate breaking config changes in minor versions. One config template file per minor version with breaking changes? One config template file per major version with logic within to handle minor version changes?
I attempted to use this formula to install
v0.9.4.1and encountered a few different errors associated with breaking config file changes introduced inv0.9.0+:In
v0.9.0, a new[meta]section was added to store clustering metadata. The current config template for0.9breaks with this error:Other changes have been introduced in minor versions like
v0.9.3that break how certain configurations sections are parsed, resulting in errors like this:I'd like to be able to help adjust the formula config files for some of these updates, but I'm not sure what pattern is recommended to accommodate breaking config changes in minor versions. One config template file per minor version with breaking changes? One config template file per major version with logic within to handle minor version changes?