5dc478db69
Instead of generated OS::TripleO::RandomString from the Heat Template, make the password generated among other passwords so we can re-use the data across undercloud-container re-install or updates, when Heat and environments are re-generated. Note: it keeps the same password constraints as it was in THT. Co-Authored-By: Dan Prince <dprince@redhat.com> Co-Authored-By: Martin André <m.andre@redhat.com> Change-Id: I9da2220ce5635d06c2ca9a21bd07eb2b6ee50aaa Related-Bug: #1736779
9 lines
337 B
YAML
9 lines
337 B
YAML
---
|
|
features:
|
|
- |
|
|
HeatAuthEncryptionKey, HorizonSecret, MysqlRootPassword, PcsdPassword
|
|
and RabbitCookie are now generated by tripleo-common among other
|
|
passwords managed by TripleO. If existing version of these parameters
|
|
have been generated by the Heat stack we first harvest those before
|
|
generating new version.
|