Age | Commit message (Collapse) | Author | Files | Lines |
|
preferable using docker-compose under csit
repo for policy in order to bring up local env
Issue-ID: POLICY-2541
Change-Id: I2e9a7e7e1cac5642228bd048def857879e580e71
Signed-off-by: Taka Cho <takamune.cho@att.com>
|
|
The databases to which the non-root policy user are
granted access are: operationshistory10 (guard) and
pooling (pooling feature).
Change-Id: Id8653e872a7750fe9e037ad2872b5541241ef4e7
Issue-ID: POLICY-788
Signed-off-by: Jorge Hernandez <jh1730@att.com>
|
|
Change-Id: I890daecb9b24bbc21c989f4e3c5fe9c4d1aa2005
Issue-ID: POLICY-788
Signed-off-by: Jorge Hernandez <jh1730@att.com>
|
|
I know some of these files should be removed, but let's
do that in a different JIRa.
Issue-ID: POLICY-741
Change-Id: Id974ff1bcfa9d34d8828e644dce337d8cdc056eb
Signed-off-by: Pamela Dragosh <pdragosh@research.att.com>
|
|
1. use mariadb image from docker registry to simplify set up.
2. remove harcoded root and user mariadb accounts
3. restrict access to user account to just specific databases.
Change-Id: Iaa916dbf2de2474fcc483a4be6167b4b92a2de61
Issue-ID: POLICY-650
Signed-off-by: Jorge Hernandez <jh1730@att.com>
|