tripleo-heat-templates/default_passwords.yaml
Dan Prince 58bf3932a8 Move MySQL settings out of puppet/controller.yaml
This moves the config settings out of controller.yaml for MySQL
and into puppet/services/database/mysql.yaml.

The top leve MysqlRootPassword is still maintained by default
in overcloud.yaml so that users who upgrade won't get
broken. New users may optionally specify the MysqlRootPassword
as a parameter instead which will take priority over the top
level generated parameter.

We drop the top level MysqlClusterUniquePart because it is no
longer used (I think it was a remnant from t-i-e).

Related-Bug: #1604414

Change-Id: I06ebac0f4c87dabfccefb2e550a64650868c5b26
2016-08-23 21:29:02 -04:00

26 lines
681 B
YAML

heat_template_version: 2016-10-14
description: Passwords we manage at the top level
parameters:
DefaultMysqlRootPassword:
type: string
DefaultRabbitCookie:
type: string
DefaultHeatAuthEncryptionKey:
type: string
DefaultPcsdPassword:
type: string
DefaultHorizonSecret:
type: string
outputs:
passwords:
description: Password data
value:
mysql_root_password: {get_param: DefaultMysqlRootPassword}
rabbit_cookie: {get_param: DefaultRabbitCookie}
heat_auth_encryption_key: {get_param: DefaultHeatAuthEncryptionKey}
pcsd_password: {get_param: DefaultPcsdPassword}
horizon_secret: {get_param: DefaultHorizonSecret}