How should we change default config values in charms?

[Richard Harding]

On Mon, 17 Aug 2015, Jorge O. Castro wrote:

> On Mon, Aug 17, 2015 at 6:03 AM, Simon Davy <bloodearnest at gmail.com> wrote:
> > Interesting. We have been defaulting to production settings, as we
> > don't want to deploy an incorrect/unsafe config in production by
> > omission, especially security related config.
>
> Interesting indeed! That's totally opposite of what I was expecting; I
> was expecting you to be explicit across the board.
>
> Also if anyone from Canonical IS can chip in I would be interested as well.

For our IS deployed services we use the Mojo tool to 'variable-ize' our
bundle/deployer file with config that changes based on the 'stage' and we
have stages for local, testing, staging, and production.

--

Rick Harding

Juju UI Engineering
https://launchpad.net/~rharding
@mitechie