Age | Commit message (Collapse) | Author | Files | Lines |
|
The sdnc-portal component is currently disabled due to known security
vulnerabilities. This component is no longer supported - the developer
left the project - and its functionality is not really needed. So, we
are removing this component in Guilin.
Issue-ID: SDNC-1236
Signed-off-by: Dan Timoney <dtimoney@att.com>
Change-Id: I45c7cad2102011fb25ca9f6707792dfd5c97624f
|
|
Whole SDNC strongly depends on the assumption that it is using a
common mariadb-galera instance and that root password is secret
password. Also user and password to sdnc DB is hardcoded.
Let's start working on removing this assumption and component by
component add support for local and shared mariadb instance without
hardcoding any passwords to the database.
In this patch all passwords are still hardcoded in the helm chart to
not break other parts of SDNC. Those values will be removed in a final patch.
Issue-ID: OOM-2309
Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com>
Change-Id: I5ca369f43e8863f9ae3ec3f5d648740808a5e099
|
|
Change-Id: I41330836901ccf1fcbdd0f9d6e720ce13ea3a9ea
Issue-ID: OOM-1651
Signed-off-by: Mahendra Raghuwanshi <mahendra.raghuwanshi@amdocs.com>
|
|
Change-Id: Ic5eda9c33abca03e2f0bc788261a3a769c5ad7ab
Signed-off-by: jmac <james.macnider@amdocs.com>
Issue-ID: OOM-970
|
|
Addressing issues like:
- missing property files
- hard-coded ports
- hard-coded ODL passwords
- improper configMap mounts
- incorrect service names
Change-Id: I74726ffedbfc20e164a814ca8777a699b92b3d65
Signed-off-by: jmac <james.macnider@amdocs.com>
Issue-ID: SDNC-310
|