commit | b6705b6d5e23c01c200131bb836a525ca41c09cf | [log] [tgz] |
---|---|---|
author | egernug <gerard.nugent@est.tech> | Wed Aug 31 14:38:24 2022 +0100 |
committer | egernug <gerard.nugent@est.tech> | Thu Dec 15 14:01:13 2022 +0000 |
tree | cfb00d5980469bd2fb5c476c36cecb96879d02b3 | |
parent | 7d81ee081cdd92a298c4fa7314c5ea3606167efa [diff] |
[SO] Generate and replace values file based on instance variable Initial DB setup for lifecycle params Create As Instance record in DB Instantiate lifecycle param check Rebase Review changes Rebase Success Test Case Amended Fail Test Case Added Issue-Id: SO-3900 Signed-off-by: egernug <gerard.nugent@est.tech> Change-Id: I68ef0562008d2d811e3fd64c81c3b6000561cb06
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.