diff options
| author |   Krzysztof Opasiak <k.opasiak@samsung.com> | 2020-02-03 21:04:22 +0100 |
|---|---|---|
| committer |   Gerrit Code Review <gerrit@onap.org> | 2020-02-03 20:04:22 +0000 |
| commit | 9cd3eb63e077ff86a55aeb90b622d5d7e9eba2d6 (patch) | |
| tree | 5181228458243f0cb7d9f49cf64d8a1a1ed69a26 /docs/submodules/vnfsdk | |
| parent | 0a0764c757755c2ce46a7b271209a0e63d3320bc (diff) | |
Update git submodules
* Update docs/submodules/oom.git from branch 'master'
to 0f3e13456f6a311786d29e7a2a560070e3d96e81
- Update git submodules
* Update kubernetes/aai from branch 'master'
to 1c9c9bba658057f6147276fba4f84e7db9117e70
- [ONAP-wide] Replace .Release.Name with common.release
ONAP is too big to be deployed using helm install so we need to
use a custom helm plugin helm deploy. This script deloys onap
component by component instead of deploying evrything at
once. Unfortunately this script also modifies the helm release by
appending component name to it.
As a result of this behavior our objects are called for example:
onap-mariadb-galera-mariadb-galera-0
instead of just being called onap-mariadb-galera-0.
This patch simplifies this naming convention by replacing all direct
usages of .Release.Name with common.release macro which strips the
component specific part from the release name.
Issue-ID: OOM-2275
Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com>
Change-Id: I450057f5b4a10842f09665ecccc58e4ed727cd89
Diffstat (limited to 'docs/submodules/vnfsdk')
0 files changed, 0 insertions, 0 deletions