On Thu, Jan 30, 2014 at 3:03 AM, Sameer Zeidat <[email protected]> wrote: > Hello, > > Not really a question, but just a thought. Would be nice if juju had a scope > added for charm config parameters, i.e. install vs. runtime. Such that it > will make those parameters needed only during deployment of a service > mutable afterwards. Instead of people writing charms silently ignoring such > changes, while juju, on the other hand, accepting and reflecting such > changes as if the had actually happened!
Hi Sameer, I've thought about this a few times with the charms I've worked on, and generally it's been possible without too much difficulty to always reflect the changes in the config_changed hook. What are a some examples of install config items that you wouldn't be able to change at runtime? (I've dealt with location of config/log files etc., versions of installed deps etc., but I'm guessing you've got something trickier). Thanks! -Michael -- Juju mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
