sandboxes/.github/workflows/deploy-microcks.yml at main · naftiko/sandboxes · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
name: Deploy Microcks to Cloudflare (DISABLED)

# ⚠️ DISABLED — 2026-06.
# mocks.naftiko.net was migrated off Cloudflare Workers + Containers to
# GCP Cloud Run (Cloudflare admin credentials were lost; see the migration
# blueprint: naftiko/blueprints/sandboxes-migration-plan.md).
#
# This workflow no longer runs: its triggers are removed so it can never
# fire against the (now inert) Cloudflare Worker. Deployment to Cloud Run is
# currently done manually (`gcloud run deploy`); a GCP-based CI job will
# replace this file later (migration plan, Phase 3).
#
# The job below is kept verbatim for historical reference only. To re-enable
# a deploy pipeline, write a new GCP workflow rather than restoring these
# Cloudflare triggers.

# No `on:` triggers — the workflow is intentionally never scheduled or run.
# (It remains manually launchable from the Actions tab only if a maintainer
# explicitly re-adds workflow_dispatch.)
on: {}

permissions:
  contents: read

# Serialize deploys — never let two run at once against the same Worker
concurrency:
  group: deploy-microcks
  cancel-in-progress: false

jobs:
  deploy:
    name: wrangler deploy
    runs-on: ubuntu-latest
    timeout-minutes: 30  # container builds + push can take a while
    steps:
      - name: Checkout
        uses: actions/checkout@v4

      - name: Setup Node
        uses: actions/setup-node@v4
        with:
          node-version: "20"
          cache: npm

      - name: Install dependencies
        run: npm ci

      # wrangler builds the container image during deploy via Buildx;
      # the runner has Docker preinstalled but Buildx needs to be set up.
      - name: Set up Docker Buildx
        uses: docker/setup-buildx-action@v3

      - name: Deploy to Cloudflare
        uses: cloudflare/wrangler-action@v3
        with:
          apiToken: ${{ secrets.CLOUDFLARE_API_TOKEN }}
          accountId: ${{ secrets.CLOUDFLARE_ACCOUNT_ID }}
          # `wrangler deploy` builds the container image (incl. baking in
          # specs/), pushes it, and rolls the Worker forward.
          command: deploy

      - name: Trigger spec import in fresh container (best-effort)
        run: |
          # The container's entrypoint serves Microcks but does not auto-run
          # import-specs.sh — that's run on demand. After a deploy, the new
          # specs are present in /specs/ inside the container; this step
          # nudges the container to import them via its REST API.
          #
          # If you've added the import-specs.sh hook to entrypoint.sh, this
          # step is redundant and can be removed.
          echo "Specs in this build:"
          ls -1 specs/ | wc -l
          echo "(import is triggered by the container's first request — no GH Action call needed)"