summaryrefslogtreecommitdiffstats
path: root/kubernetes/policy/charts/drools/resources/configmaps/base.conf
diff options
context:
space:
mode:
authorKrzysztof Opasiak <k.opasiak@samsung.com>2019-11-21 22:48:12 +0100
committerKrzysztof Opasiak <k.opasiak@samsung.com>2019-11-21 23:00:37 +0100
commitc6f8706f751312eab1487460352e219af9ace3c9 (patch)
treed39a12359fd8f313daf98fec67682ec01fd0135f /kubernetes/policy/charts/drools/resources/configmaps/base.conf
parent17804e20a22090d3c0b2333528dd6f0ca7809567 (diff)
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 'kubernetes/policy/charts/drools/resources/configmaps/base.conf')
0 files changed, 0 insertions, 0 deletions