Fix handling of blank moduleSetTag 28/137328/1
authordanielhanrahan <daniel.hanrahan@est.tech>
Wed, 21 Feb 2024 10:02:19 +0000 (10:02 +0000)
committerdanielhanrahan <daniel.hanrahan@est.tech>
Wed, 21 Feb 2024 10:58:31 +0000 (10:58 +0000)
commit18316c037509c4fddf382d8512c6af620019c7b8
tree278072f181f30a674fb288a25b85a41c00c5020d
parentcbd20a33ea2414a02a3a3fba79ddc734f51e77ac
Fix handling of blank moduleSetTag

Handling of blank moduleSetTag is very inconsistent.
Sometimes it will be returned as null, '' or 'not-specified'.
Specifically in the case of MODULE_UPGRADE_FAILED, on the retry,
a blank moduleSetTag will be returned as 'not-specified', leading
to incorrect upgrade.

Issue-ID: CPS-2027
Signed-off-by: danielhanrahan <daniel.hanrahan@est.tech>
Change-Id: I3f4290dc5659c386c7b2b924325da2560d00d73b
cps-ncmp-service/src/main/java/org/onap/cps/ncmp/api/impl/inventory/sync/ModuleOperationsUtils.java
cps-ncmp-service/src/main/java/org/onap/cps/ncmp/api/impl/inventory/sync/ModuleSyncService.java
cps-ncmp-service/src/test/groovy/org/onap/cps/ncmp/api/impl/inventory/sync/ModuleOperationsUtilsSpec.groovy