...
Components Name | Components Repository name | Maven Group ID Gildas Lanilis ? question - originally I had a single pomba group ID - and differentiated by the artifact ID Do we need the distinct group ID per repo because of an LF jjb requirement? just wondering Looks like we need to be distinct here - to protect against a duplicate artifact ID across 2 repos | Components Description |
---|---|---|---|
logging-analytics | logging-analytics | org.onap.logging-analytics | A reference analytics pipeline configuration |
pomba-context-aggregator | logging-analytics/pomba/pomba-context-aggregator | org.onap.pomba.pomba-context-aggregator (all below previously org.onap.pomba) with differentiators in the Maven artifact ID) | Orchestrates calls to various context builders and aggregates data from various data sources into one single payload |
pomba-aai-context-builder | logging-analytics/pomba/pomba-aai-context-builder | org.onap.pomba.pomba-aai-context-builder | AAI Context builder. Interacts with A&AI and transforms A&AI data into common model structure |
pomba-sdc-context-builder | logging-analytics/pomba/pomba-sdc-context-builder | org.onap.pomba.pomba-sdc-context-builder | SDC Context builder. Interacts with SDC and transforms SDC TOSCA CSAR into common model structure |
pomba-sdnc-context-builder | logging-analytics/pomba/pomba-sdnc-context-builder | org.onap.pomba.pomba-sdnc-context-builder | SDN-C Context Builder. Interacts with SDN-C and transforms SDN-C data into common model structure |
pomba-network-discovery-context-builder | logging-analytics/pomba/pomba-network-discovery-context-builder | org.onap.pomba.pomba-network-discovery-context-builder | Network Discovery Context Builder. Interacts with Network discovery component and transforms its data into common model structure |
pomba-audit-common | logging-analytics/pomba/pomba-audit-common | org.onap.pomba.pomba-audit-common | POJO project. Holds POMBA common model POJO representation |
...