Decouple application configuration file

Agreement is that application configuration should live on OOM
- leave an example of the configuration file under docker
  compose to run locally, instead of use OOM. Mainly for devs
- document on README how to run the app with IDE or with docker compose
- remove duplicate code on poms

Issue-ID: CPS-175
Signed-off-by: Claudio D. Gasparini <claudio.gasparini@pantheon.tech>
Change-Id: I328e89dba78cdf4d8abab51e3be5cb6d641064db
5 files changed
tree: fd803e64387205147eda40668532a1aa053f7376
  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