https://wiki.onap.org/display/DW/CPS-677+Support+%27public%27+Cm+Handle+Properties

• like cmHandleProperties but these properties are NOT used by DMI-Plugin.
• NCMP will forward these properties on northbound interface (clients)
• Required additional REST endpoint for
  • get cm-handle by  name
  • Should this return all properties or just public properties?
• Write wiki page outlining liquibase changelog procedures.
• Add new public properties to dmi-registry yang resource.
  • Could potentially have same names
• Add new revision number for updated existing yang resource.
• Public properties should be optional

A/C

1. Share and agree with team wiki on liquibase process
2. Share and agree new with team schema for public properties.
3. Implement changes to body of register cm-handles API.
4. Write CSIT for End to End testing with public properties.
5. Demo new endpoint to team with public properties & without public properties.
6. Update Wikipage outlining liquibase changelog procedures

Out of Scope

1. Query cm-handles by public properties.

Open Issues

1. Will this affect existing REST endpoint(s) for
   • list cm handles that have certain module(s)