summaryrefslogtreecommitdiffstats
path: root/docs/submodules/oom.git
diff options
context:
space:
mode:
authorMike Elliott <mike.elliott@amdocs.com>2019-12-04 13:26:05 +0000
committerGerrit Code Review <gerrit@onap.org>2019-12-04 13:26:05 +0000
commitc33213f1fdec682250f8ac4a1a8241f68946b5ae (patch)
treeb4d1da8e0d8e1b1eb5a6bed4c929740c276a2206 /docs/submodules/oom.git
parentd12384c7c1568d30780407cb24bde80edcf5e68d (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/oom.git')
m---------docs/submodules/oom.git0
1 files changed, 0 insertions, 0 deletions
diff --git a/docs/submodules/oom.git b/docs/submodules/oom.git
-Subproject b16e8fe5947741d6c6c7f3458a87a6efa6a2285
+Subproject e21978408ab1bee4c571bbb6cc58904d3ee3647