name: "DevSecOps Enterprise Pipeline"

# ALTERADO: Agora a pipeline reage a QUALQUER alteração em QUALQUER branch,
# permitindo a automação total sem intervenção manual.
on:
  push:
    branches: ["*"] # Escuta todas as branches
  pull_request:
    branches: [ main ]

jobs:
  security-gate-and-deploy:
    runs-on: ubuntu-latest
    steps:
      - name: 0. Checkout Code
        uses: actions/checkout@v3
        with:
          fetch-depth: 0

      # ==========================================
      # ETAPA 1: VALIDACAO FUNCIONAL (TESTES UNITÁRIOS)
      # Correm SEMPRE, em qualquer branch.
      # ==========================================
      - name: 1.1. Setup Node.js Environment
        uses: actions/setup-node@v3
        with:
          node-version: '18'

      - name: 1.2. Run Unit Tests (Jest)
        run: |
          echo ">>> A instalar dependências e a correr testes funcionais..."
          # Ajusta para a pasta onde tens o teu package.json (ex: cd backend && npm install)
          npm install
          npm test

      - name: 1.3. Build Application Image
        run: docker build -f backend/Dockerfile -t apex-solutions:latest .

      # ==========================================
      # ETAPA 2: ANÁLISE ESTÁTICA RÁPIDA (SAST, SCA)
      # Correm SEMPRE, a cada commit de qualquer branch secundária.
      # ==========================================

      - name: 2.1. Secret Scanning (Gitleaks)
        run: |
          curl -sL https://github.com/gitleaks/gitleaks/releases/download/v8.18.2/gitleaks_8.18.2_linux_x64.tar.gz | tar -xz -C /tmp
          /tmp/gitleaks detect --source . --verbose --redact --log-opts="-1" --exit-code 1

      - name: 2.2. Software Composition Analysis (Trivy)
        run: |
          curl -sfL https://raw.githubusercontent.com/aquasecurity/trivy/main/contrib/install.sh | sh -s -- -b /usr/local/bin
          trivy image --severity HIGH,CRITICAL --format table --output trivy-report.txt apex-solutions:latest
          trivy image --severity HIGH,CRITICAL --exit-code 1 apex-solutions:latest

      - name: 2.3. Archive Trivy Report
        if: always()
        uses: actions/upload-artifact@v3
        with:
          name: trivy-sca-report
          path: trivy-report.txt

      - name: 2.4. Static Application Security Testing (SonarQube)
        run: |
          curl -sL https://binaries.sonarsource.com/Distribution/sonar-scanner-cli/sonar-scanner-cli-5.0.1.3006-linux.zip -o sonar-scanner.zip
          unzip -q sonar-scanner.zip
          ./sonar-scanner-5.0.1.3006-linux/bin/sonar-scanner \
            -Dsonar.projectKey=website-test \
            -Dsonar.sources=. \
            -Dsonar.host.url=https://sonar.each-cs.com \
            -Dsonar.token=${{ secrets.SONAR_TOKEN }} \
            -Dsonar.qualitygate.wait=true

      # ==========================================
      # ETAPA 3: ANÁLISE DINÂMICA (DAST - OWASP ZAP)
      # CRÍTICO: O condicional 'if' garante que este bloco SÓ corre na branch 'main'
      # ==========================================

      - name: 3.1. Provision Ephemeral Sandbox
        if: github.ref == 'refs/heads/main'
        run: |
          docker rm -f website-test-sandbox || true
          docker run -d --name website-test-sandbox apex-solutions:latest
          sleep 5

      - name: 3.2. OWASP ZAP Baseline Scan
        if: github.ref == 'refs/heads/main'
        run: |
          mkdir -p qatests
          docker rm -f zap-scanner || true
          docker volume rm zap-reports || true
          docker volume create zap-reports
          
          docker run --user root --name zap-scanner \
            --link website-test-sandbox:website-test-sandbox \
            -v zap-reports:/zap/wrk/:rw \
            -t ghcr.io/zaproxy/zaproxy:stable zap-baseline.py \
            -t http://website-test-sandbox:3000 \
            -r report.html \
            -I
          
          docker cp zap-scanner:/zap/wrk/report.html qatests/report.html
          docker rm -f zap-scanner || true
          docker volume rm zap-reports || true

      - name: 3.3. Teardown Ephemeral Sandbox
        if: always() && github.ref == 'refs/heads/main'
        run: |
          docker rm -f website-test-sandbox || true

      # ==========================================
      # ETAPA 4: DEPLOY SEGURO VIA SSH
      # CRÍTICO: Só executa se passar em TUDO e for um push final na branch 'main'
      # ==========================================

      - name: 4.1. Hardened Production Deployment via SSH
        if: github.ref == 'refs/heads/main' && github.event_name == 'push'
        uses: appleboy/ssh-action@v1.0.0
        with:
          host: ${{ secrets.SSH_HOST }}
          username: ${{ secrets.SSH_USER }}
          key: ${{ secrets.SSH_PRIVATE_KEY }}
          script: |
            echo ">>> A iniciar o Deploy Remoto em Produção via SSH..."
            cd /opt/website-test
            git pull origin main
            
            # Tratamento do .env em produção usando os Secrets do Gitea
            echo "PORT=3000" > .env
            echo "API_SECRET=${{ secrets.API_SECRET_PROD }}" >> .env
            
            # Reconstrói a imagem e reinicia o serviço refletindo o espelho da main
            docker build -f backend/Dockerfile -t apex-solutions:production .
            docker stop portal-corporativo || true
            docker rm portal-corporativo || true
            docker run -d -p 3000:3000 --env-file .env --name portal-corporativo apex-solutions:production
            echo ">>> Deploy em Produção finalizado com sucesso!"

      # ==========================================
      # ETAPA 5: GESTÃO DE ARTEFACTOS
      # ==========================================

      - name: Archive ZAP Report (Raw HTML)
        if: always() && github.ref == 'refs/heads/main'
        uses: actions/upload-artifact@v3
        with:
          name: owasp-zap-report
          path: qatests/report.html