e41a552afe
Previous configuration file management method used templates. This method had limited flexibility and was cumbersome to use and maintain between upstream versions. This change introduces new custom types based on ini_setting: * swift_account_config: /etc/swift/account-server.conf * swift_bench_config: /etc/swift/swift-bench.conf * swift_config: /etc/swift/swift.conf * swift_container_config: /etc/swift/container-server.conf * swift_dispersion_config: /etc/swift/dispersion.conf * swift_object_config: /etc/swift/object-server.conf * swift_proxy_config: /etc/swift/proxy-server.conf The use of ini_setting offers multiple advantages: * Ability to individually manage configuration settings without the need to modify templates. This allows the user to manage or override settings that aren't handled by the module. * Use upstream default values if none is provided. * Remove the need to maintain and synchronize templates to match upstream versions. Such maintenance could become problematic and complicated if multiple upstream versions are supported but have different base configuration files. Implements: blueprint puppet-swift-ini-settings Change-Id: Iba7be64581b81b8ab4f33cf7096df37e64ccc4b4 |
||
---|---|---|
.. | ||
ini_setting.rb |