fix(zap): Update runs-on to ubuntu-22.04, Add retry mechanism, Modify run-ci command, Remove --wait flag

.github/workflows/zap-scanner.yaml

@@ -2,24 +2,27 @@ name: ZAP Scan
 on:
   push:
     branches:
-      - main
+      - feat/fix-zap-tests
 permissions:
   issues: write
 jobs:
   zap_scan:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-22.04
     name: Scan the webapplication
     steps:
       - uses: actions/checkout@v4
       - uses: extractions/setup-just@v2
       # This step builds the image and runs the web application in the background for the ZAP scan
       - name: Run image
-        run: just run-ci
+        run: |
+          just run-ci
+          curl --retry 5 --retry-connrefused --retry-max-time 120 -k -s https://127.0.0.1/health
+
       - name: ZAP Scan
         uses: zaproxy/action-api-scan@v0.7.0
         with:
           token: ${{ secrets.GITHUB_TOKEN }}
           format: openapi
-          target: 'https://localhost:8443/openapi.json'
+          target: 'https://127.0.0.1/openapi.json'
           # The '-a' option activates all active scanners. Use this for comprehensive scanning.
           cmd_options: '-a'

justfile

@@ -51,8 +51,8 @@ run: build
     docker run -it -p 5000:5000 -e ENVIRONMENT=development -v $pwd/data:/data test-actions
 
 # Use this command to run the application in CI/CD pipeline
-run-ci: build
-    docker-compose up -d --wait
+run-ci:
+    docker-compose up -d
 
 # Use this command to run the application in development mode in your local machine,
 # using your local source code, without the need to rebuild the image. Don't use it if you're