Hi all, I need some consensus on how to handle merge proposals for charms in the charm charm store when these proposals change configuration key names. The proposal in question is https://code.launchpad.net/~sidnei/charms/precise/squid-reverseproxy/trunk/+merge/190500 in the config.yaml diff the following is changed:
320- nagios_check_url:321+ nagios_check_http_params:322 default: ""323type: string 324 description: >325- The URL to check squid has access to, most likely inside your web server farm326+ The parameters to pass to the nrpe plugin check_http. It's my understanding we do not want to change configuration option names as it will "break" what a user has deployed. Configuration values can be added, as sane defaults will kick in with that but when it comes to changing a name it's essentially removing that configuration option and adding a new one. I would recommend in this scenario that nagios_check_url remains and nagios_check_http_params is added with the change and note of the distinction of the two in the README. I'm actually not sure how to handle this though, so I'm reaching out to the list for feedback. Thanks, Marco Ceppi
-- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
