summaryrefslogtreecommitdiffstats
path: root/kubernetes/sdnc/charts/sdnc-portal/resources/config/svclogic.properties
AgeCommit message (Collapse)AuthorFilesLines
2020-08-24[SDNC] Remove sdnc-portal componentDan Timoney1-5/+0
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
2020-02-24[SDNC] Use common secret template in sdnc-portalKrzysztof Opasiak1-4/+4
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
2018-05-30make sdnctl user db password configurable for SDNCjmac1-1/+1
Change-Id: Ic5eda9c33abca03e2f0bc788261a3a769c5ad7ab Signed-off-by: jmac <james.macnider@amdocs.com> Issue-ID: OOM-970
2018-04-18Fixes for SDNC portal podjmac1-0/+5
With these changes, the SDNC Portal pod is now coming up cleanly and there are no errors in the logs. I was able to successfully create a user and log in to the portal. Change-Id: Iab3374c585a0b88844e83860d14e572e151958a6 Signed-off-by: jmac <james.macnider@amdocs.com> Issue-ID: OOM-881