diff options
author | Sylvain Desbureaux <sylvain.desbureaux@orange.com> | 2020-02-19 16:00:03 +0000 |
---|---|---|
committer | Gerrit Code Review <gerrit@onap.org> | 2020-02-19 16:00:03 +0000 |
commit | ad5ae5aa3b2c4bbc4ccc9e26a54802f8c528c747 (patch) | |
tree | 385fd4576e33e2b2fbd232974dd274f174cd8f3e /docs/release-notes.rst | |
parent | baf258aa4d3af5957f6efcab8953a6d71078b42d (diff) |
Update git submodules
* Update docs/submodules/oom.git from branch 'master'
to 314512b9085a672195a1aad27e922cf1e791b780
- Merge "[COMMON] Use common secret template in dgbuilder"
- [COMMON] Use common secret template in dgbuilder
Taken into account how "easy" it would be to modify the dgbuilder
which is written in JavaScript (which is not my mother tongue to say
the least) let's try to remove hardcoded passwords from config files
without modifying the application container itself.
In order to achieve this:
1) Remove createReleaseDir.sh script from the container as it is never
used and contains a ton of passwords
2) Replace all sensitive values in config files with references to
respective environment variables
3) Introduce init container that will run envsubst command on config
files and copy them from ConfigMap value to the new volume which is
backed by tmpfs so that the plain text passwords are never written to
the disk
For now all the hardcoded values are still there to minimize the risk
of breaking the deployment but step by step they will be removed in
next commits.
Issue-ID: OOM-2247
Change-Id: I5a428e3415713857084ba6aaa6be9b04a8eb8c0f
Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com>
Diffstat (limited to 'docs/release-notes.rst')
0 files changed, 0 insertions, 0 deletions