Decouple configuration from application

- Decouple configuration from application
- Generate all 3 types of docker variations

Issue-ID: CPS-175
Signed-off-by: Claudio D. Gasparini <claudio.gasparini@pantheon.tech>
Change-Id: I1e2e0577c5911f7c79801e4c691d196515dc02a1
22 files changed
tree: 74556b527ac48ac608db2d420929785c797a6a07
  1. checkstyle/
  2. cps-application/
  3. cps-bom/
  4. cps-dependencies/
  5. cps-nf-proxy-rest/
  6. cps-parent/
  7. cps-rest/
  8. cps-ri/
  9. cps-service/
  10. docker-compose/
  11. spotbugs/
  12. .gitignore
  13. .gitreview
  14. INFO.yaml
  15. LICENSE.txt
  16. pom.xml
  17. README.md
  18. version.properties
README.md

Configuration Persistence Service

This folder contains all files for Configuration Persistence Service.

The code here is related to CPS POC, then it must be kept self contained in this cps folder to prevent any impact on current ccsdk components and to be ready to be moved in its own repo once CPS becomes a standalone project.

Running Locally

  • Run a postgres container instance and create `cpsdb' database:
CREATE USER cps WITH PASSWORD 'cps';
CREATE DATABASE cpsdb OWNER cps;
  • Build (from cps root folder)
mvn clean package
  • Run (from cps root folder)
java -DDB_HOST=localhost -DDB_USERNAME=cps -DDB_PASSWORD=cps -jar cps-rest/target/cps-rest-0.0.1-SNAPSHOT.jar