diff options
author | Mike Elliott <mike.elliott@amdocs.com> | 2019-12-04 13:26:05 +0000 |
---|---|---|
committer | Gerrit Code Review <gerrit@onap.org> | 2019-12-04 13:26:05 +0000 |
commit | c33213f1fdec682250f8ac4a1a8241f68946b5ae (patch) | |
tree | b4d1da8e0d8e1b1eb5a6bed4c929740c276a2206 /docs/submodules/policy | |
parent | d12384c7c1568d30780407cb24bde80edcf5e68d (diff) |
Update git submodules
* Update docs/submodules/oom.git from branch 'master'
to e21978408ab1bee4c571bbb6cc58904d3ee36472
- Merge "Add password generation template"
- Add password generation template
Currently there is a number of hardcoded passwords in OOM helm charts
that are reused for almost all ONAP deployments in different labs.
One possible solution for this issue could be to generate a random
password for every deployment but this may cause number of issues
while doing helm upgrade.
That's why instead of generating a random password we generate a
password for particular use case, based on chart name, master
password provided by the deployer and additional UID. This is done
using derivePassword function so check its documentation for more
details how this password is derived.
From a user perspective, the most important fact is that he or she can
achieve reproductible deployment. Every time when ONAP is deployed
with the same masterPassword all derived passwords are going
to be also the same.
Issue-ID: OOM-2052
Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com>
Change-Id: I666d597e6daab8b79e630917ad75f17cc70f897b
Diffstat (limited to 'docs/submodules/policy')
0 files changed, 0 insertions, 0 deletions