aboutsummaryrefslogtreecommitdiffstats
path: root/components/model-catalog/proto-definition/proto/BluePrintManagement.proto
diff options
context:
space:
mode:
authorJuhi Arora <juhi.arora1@bell.ca>2022-06-06 13:30:03 -0400
committerkuldipr <kuldip.rai@amdocs.com>2022-09-01 08:48:15 -0400
commit89c17ae2e3222b98450e7c8d17566cd76ecf113b (patch)
treed8ca903df5dd3c189d87aef3dac6065f22e1b303 /components/model-catalog/proto-definition/proto/BluePrintManagement.proto
parente8e0087c6aea0bf9b2d3d17207574e8db84ba0f3 (diff)
CDS max-occurrence feature
As part of occurrence feature, one or more version of the resource resolution can be resolved. However, user did not have granular control in case the user wants to resolve a specific value once and never again. Max-Occurrence feature implements the granular control to be give the user an option to specify the max number of times a resource to be resolved. It is specified as part of mapping in a cba. Max-occurrence value of 0 or not specifying it explicitly denotes the current default behaviour of unlimited resoltions. If a user specify a particular max-occurrence value then the resource is resolved that many times in subsquent requests and never again once we reached the max-occurrence limit of resource resolutions. Issue-ID: CCSDK-3736 Change-Id: Ie18764a313530e36be14531d8c7b93bf54f0b651 Signed-off-by: kuldipr <kuldip.rai@amdocs.com>
Diffstat (limited to 'components/model-catalog/proto-definition/proto/BluePrintManagement.proto')
0 files changed, 0 insertions, 0 deletions