Fixed bug in CVS test logic

The -f test with a wildcard works OK if there is 0 or 1 CSV files but
breaks if there are 2 or more. The replacement uses ls to check if
there are any CSV files.
This commit is contained in:
Croft 2024-06-07 16:08:16 +02:00
parent aa122d0bff
commit a738f1468f
1 changed files with 2 additions and 2 deletions

View File

@ -56,7 +56,7 @@ services:
command: bash -c " \ command: bash -c " \
echo listing /app/data && \ echo listing /app/data && \
ls -la /app/data && \ ls -la /app/data && \
[ -f /app/data/*.[cC][sS][vV] ] && \ ls /app/data/*.[cC][sS][vV] 1> /dev/null 2>&1 && \
[ ! -f /app/data/lock ] && \ [ ! -f /app/data/lock ] && \
( \ ( \
echo 'Wait for Blaze to finish initializing' ; \ echo 'Wait for Blaze to finish initializing' ; \
@ -78,5 +78,5 @@ services:
test-data-loader: test-data-loader:
container_name: test-data-loader container_name: test-data-loader
image: samply/test-data-loader image: samply/test-data-loader
command: sh -c "sleep 300 && echo Listing all resources in FHIR store && blazectl --server http://bridgehead-bbmri-blaze:8080/fhir count-resources && tail -f /dev/null" command: sh -c "sleep 400 && echo Listing all resources in FHIR store && blazectl --server http://bridgehead-bbmri-blaze:8080/fhir count-resources && tail -f /dev/null"