[patch] Fix maximoit test record label (#266)

Author: whitfiea

instance-applications/510-550-ibm-mas-suite-app-config/templates/04-postsync-maximoit-verify.yaml

@@ -1,9 +1,8 @@
 {{- if eq .Values.mas_app_id "manage" }}
 {{- if and (.Values.mas_appws_spec.components) (.Values.mas_appws_spec.components.icd) }}
 
-# A sanity test is one that can be disruptive i.e. it can create new users, call authenticated apis, creates resources 
-# in the application. This type of test should only be run in a downstream environment such as a dev or staging env
-# The control over if these tests run or not is controlled by the `run_sanity_test` boolean in the values
+# A verify test is one that is non disruptive i.e. it won't create new users, i won't call authenticated apis, and it won't creates resources 
+# in the application. This type of test is run on every environment and allows a layer of verification of the app
 
 {{ $ns               :=  .Values.mas_app_namespace }}
 {{ $np_name          :=  "postsync-verify-maximoit-np" }}
@@ -404,7 +403,7 @@ metadata:
     argocd.argoproj.io/hook: PostSync
     argocd.argoproj.io/hook-delete-policy: BeforeHookCreation
   labels:
-    type: mas-app-sanity-record
+    type: mas-app-verification-record
 {{- if .Values.custom_labels }}
 {{ .Values.custom_labels | toYaml | indent 4 }}
 {{- end }}