"wait_for_status=yellow" does never get reached

[bap-dev]

In edusharing-repository-service the check in the entrypoint.sh wait_for_status=yellow for the search-elastic index does never get caught, because at least in our cluster the status jumps to green very fast. I changed yellow to green and replaced also the missing env in that container with existing ones. Also a general question is why is it better to check for yellow states instead of green states? Here is my command section in the statefulset of the repository-service, which starts the container without errors:

`... containers:

• name: {{ include "edusharing_common_lib.names.name" . }}-server image: {{ include "edusharing_common_lib.images.image" . }}{{ .Values.image.name }}:{{ .Values.image.tag }} imagePullPolicy: {{ .Values.global.image.pullPolicy }} command:
  • "/bin/bash"
  • "-c"
  • | sed -i 's/REPOSITORY_SEARCH_ELASTIC_INDEX_HOST/EDUSHARING_REPOSITORY_SEARCH_ELASTIC_INDEX_SERVICE_HOST/g' /opt/alfresco/bin/plugins/plugin-elastic/entrypoint.sh sed -i 's/REPOSITORY_SEARCH_ELASTIC_INDEX_PORT/EDUSHARING_REPOSITORY_SEARCH_ELASTIC_INDEX_SERVICE_PORT/g' /opt/alfresco/bin/plugins/plugin-elastic/entrypoint.sh sed -i 's/wait_for_status=yellow/wait_for_status=green/' /opt/alfresco/bin/plugins/plugin-elastic/entrypoint.sh /opt/alfresco/bin/entrypoint.sh /opt/bitnami/scripts/tomcat/run.sh ....` cheers