Hi Jimmy and Harish,
The cloud-region schema element is unusual in that it has a two-part key i.e.
"cloud-owner" and "cloud-region-id". There are not many other usages of it
("ctag-pool" , "service-capability" and "route-target" are three others, out of
over 100 other schema elements)
Is it possible to enhance the error message to indicate that part of the key
value is missing from the relationship-data?
Is it time to deprecate the relationship-data and switch over to using the
related-link only?
Is there any modeling guidance that would steer new designs away from using
multi-part key for schema elements?
Are there other caveats to using the multi-part key design for schema elements?
Keong
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#16675): https://lists.onap.org/g/onap-discuss/message/16675
Mute This Topic: https://lists.onap.org/mt/31317665/21656
Group Owner: [email protected]
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
