[patch] fix automated initial user creation when Manage is not installed

instance-applications/600-ibm-post-sync-jobs/templates/001-ibm-create-initial-users.yaml

@@ -53,8 +53,7 @@ $_job_cleanup_group can usually just be based on $_job_name_prefix. There are so
 where multiple Jobs are created in our templates using a Helm loop. In those cases, additional descriminators
 must be added to $_job_cleanup_group.
 
-By convention, we sha1sum this value to guarantee we never exceed the 63 char limit regardless of which discriminatorstest python-devops bui
-are required here.
+By convention, we sha1sum this value to guarantee we never exceed the 63 char limit regardless of which discriminators are required here.
 
 */}}
 {{- $_job_cleanup_group := cat $_job_name_prefix | sha1sum }}
@@ -184,6 +183,12 @@ roleRef:
   apiGroup: rbac.authorization.k8s.io
 
 
+{{- /*
+mas-devops-create-initial-users-for-saas script run by the Job requires access to the xxx-internal-manage-tls
+secret in the manage namespace so it can create an API Key for the MAXADMIN user
+Since these roles must be created in the manage namespace, we only attempt to create them if Manage is actually installed.
+*/}}
+{{- if .Values.manage_is_installed }}
 ---
 kind: Role
 apiVersion: rbac.authorization.k8s.io/v1
@@ -224,7 +229,7 @@ roleRef:
   kind: Role
   name: {{ $role_manage_name }}
   apiGroup: rbac.authorization.k8s.io
-
+{{- end }}
 
 ---
 apiVersion: batch/v1

root-applications/ibm-mas-instance-root/templates/600-ibm-post-sync-jobs.yaml

@@ -59,6 +59,7 @@ spec:
             {{- end }}
 
             mas_is_active: {{ $mas_is_active }}
+            manage_is_installed: {{ not (empty .Values.ibm_suite_app_manage_install) }}
 
             {{- if .Values.custom_labels }}
             custom_labels: {{ .Values.custom_labels | toYaml | nindent 14 }}