commit | 26714e691a2077a5e190b3da3e0824321a7429a1 | [log] [tgz] |
---|---|---|
author | nadeeshani.jayathilake <nadeeshani.jayathilake@est.tech> | Mon Nov 21 09:53:15 2022 +0000 |
committer | nadeeshani.jayathilake <nadeeshani.jayathilake@est.tech> | Mon Nov 21 11:40:50 2022 +0000 |
tree | 34a17e2704ec261fdfefbad439724b988bbadb5f | |
parent | 0b66a66b33959aeaaa76ad6967d922c8d543023b [diff] |
Helm charts values customization using files Issue-ID: SO-4030 Signed-off-by: nadeeshani.jayathilake <nadeeshani.jayathilake@est.tech> Change-Id: I1fea315e3f39179161a32762ca53763088426520
SO CNFM project which handles the AS/CNF Lifecycle Management.
SO CNFM can be compiled with mvn clean install
Subscribe and post messages with SO tag in onap-discuss group at https://lists.onap.org/g/onap-discuss
SO-CNFM is composed of a main pom.xml which is structured to build packages (docker image preparation file) and so-cnfm-lcm modules. Also, so-cnfm-lcm is structured to build all submodules and there is individual pom.xml for each submodule. so-cnfm-lcm is composed of so-cnfm-lcm-api – generates the POJOs for REST APIs. so-cnfm-lcm-application – creates Spring Boot application jar file. so-cnfm-lcm-bpmn-flows - Camunda BPM engine code flow for step-by-step order flow execution. so-cnfm-lcm-database-service – mariadb for storing metadata. so-cnfm-lcm-service – contains the REST APIs.