Versions Compared

Old Version 34

changes.mady.by.user Joseph Keenan

Saved on

compared with

New Version 35

changes.mady.by.user Joseph Keenan

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...


IssueNotesDecision
1Does request body need to declare "publicCmHandleProperties"?

Do we need to explicitly declare "publicCmHandleProperties"? 

Will there be another possible variation to this in the future?

Code Block
languageyml
{
  "publicCmHandleProperties" : {
          "Name-1" : "some-value",
          "Name-2" : "other-value"
   }
}


Yes
2Are public properties always be in the format of "name" : x, "value": y?

In the fragment table there are example that follow this format 

Code Block
languageyml
{
	"name": "Contact",
	"value": "newemailforstore@bookstore.com"
}


Yes.


3Will there only ever be 1 kv pairs in public properties?
Yes
4Does the order matter?

Does

Code Block
languageyml
{
  "publicCmHandleProperties" : {
          "Name-1" : "some-value",
          "Name-2" : "other-value"
   }
}

==

Code Block
languageyml
{
  "publicCmHandleProperties" : {
          "Name-2" : "other-value",
          "Name-1" : "some-value"
   }
}


No
5Should search be case sensitive?

depend on CPSPath functionality - may be case-sensitive

https://docs.onap.org/projects/onap-cps/en/latest/cps-path.html

Investigation Pending
6What format should the response take?

We have two options currently:


  1. Return List<String>


Code Block
languageyml
[
    "cmHandle1",
    "cmHandle2",
    ...,
    "cmHandleN"
]


2. Return CM Handle Objects

    1. Already defined in CPS
    2. <Example Pending>


Contact Tony Finnerty & kieran mccarthy regarding this.

Tony Finnerty Has no opinion on this matter


Analysis/Implementation Proposal

...