Policy suggestion for charm store regarding config.yaml and passwords...

[Clint Byrum]

Excerpts from Patrick Hetu's message of Tue Mar 20 17:23:13 -0700 2012:
> I have try to think about a way to generate a password with pwgen and
> then send it back to
> the user. One thing that could solve the problem would be a
> "config-set" command that allows
> charm's hook to set a password. The user will then use a command like
> `juju get admin_password`
> to get the password. But that might lead to other issues.

Another way to go is to just have the ability to define functions as
defaults and have a 'password(length)' function available. This way on
deploy, if no value was specified, it would be generated, and available as
'juju get myservice password' immediately after an automated deployment
script runs.

For now, the charm should probably just use juju-log to inform the user
about it, and they can extract it from debug-log or the charm log if
need be. Another option is to error out with a message informing the
user that this setting is required.

Anyway, I went ahead and added the policy. If you see default passwords
in use in existing charms, please file a critical bug in the charm. If
you are a member of charmers, please *fix* that bug. :)