fix validate logic

images/kubectl-build-deploy-dind/build-deploy-docker-compose.sh

@@ -181,21 +181,22 @@ if kubectl -n ${NAMESPACE} get configmap docker-compose-yaml &> /dev/null; then
   # create it
   kubectl -n ${NAMESPACE} create configmap docker-compose-yaml --from-file=pre-deploy=${DOCKER_COMPOSE_YAML}
 fi
-
+set +ex
 ##############################################
 ### RUN docker compose config check against the provided docker-compose file
 ### use the `build-validate` built in validater to run over the provided docker-compose file
 ##############################################
 dccOutput=$(bash -c 'build-validate validate docker-compose --docker-compose '${DOCKER_COMPOSE_YAML}' --ignore-non-string-key-errors=false; exit $?' 2>&1)
 dccExit=$?
+echo "docker-compose validate exit code ${dccExit}: ${dccOutput}"
+
 if [ "${dccExit}" != "0" ]; then
   currentStepEnd="$(date +"%Y-%m-%d %H:%M:%S")"
   patchBuildStep "${buildStartTime}" "${previousStepEnd}" "${currentStepEnd}" "${NAMESPACE}" "dockerComposeValidationError" "Docker Compose Validation Error"
   previousStepEnd=${currentStepEnd}
   # the warning message is displayed at the end of the build
 fi
-
-set -x
+set -ex
 
 # validate .lagoon.yml
 if ! lagoon-linter; then
@@ -1625,11 +1626,11 @@ if [ "${dccExit}" != "0" ]; then
 Warning!
 There are issues with your docker compose file that lagoon uses that should be fixed.
 This does not currently prevent builds from proceeding, but future versions of Lagoon *will* be more strict on issues shown here.
-You can run `docker compose config` locally to check that your docker-compose file is valid.
+You can run docker compose config locally to check that your docker-compose file is valid.
 ##############################################
 "
   echo ${dccOutput}
   echo "
 ##############################################"
 fi
-set -x
+set -x