aks-auto-start.yaml

name: aks-auto-start
on:
  workflow_dispatch:
  schedule:
    - cron: "30 6 * * 1-5" # Every weekday at 6:30am BST
env:
  DEV_ENV: ${{ secrets.DEV_ENV }}
permissions:
  id-token: write
jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout
        uses: actions/checkout@v4

      - name: "Az CLI login"
        uses: azure/login@v2
        with:
          client-id: 2b6fa9d7-7dba-4600-a58a-5e25554997aa # DTS AKS Auto-Shutdown
          tenant-id: 531ff96d-0ae9-462a-8d2d-bec7c0b42082 # HMCTS.NET
          allow-no-subscriptions: true

      - name: Staging - AKS Auto Start
        run: ./scripts/aks/auto-start-stop.sh start staging
        env:
          DEV_ENV: ${{ env.DEV_ENV }}

      - name: Test - AKS Auto Start
        run: ./scripts/aks/auto-start-stop.sh start testing
        env:
          DEV_ENV: ${{ env.DEV_ENV }}

      - name: Demo - AKS Auto Start
        run: ./scripts/aks/auto-start-stop.sh start demo
        env:
          DEV_ENV: ${{ env.DEV_ENV }}

      - name: Development - AKS Auto Start
        run: ./scripts/aks/auto-start-stop.sh start development
        env:
          DEV_ENV: ${{ env.DEV_ENV }}

      - name: Sandbox - AKS Auto Start
        run: ./scripts/aks/auto-start-stop.sh start sandbox
        env:
          DEV_ENV: ${{ env.DEV_ENV }}

      - name: ITHC - AKS Auto Start
        run: ./scripts/aks/auto-start-stop.sh start ithc
        env:
          DEV_ENV: ${{ env.DEV_ENV }}

      #Production is referenced here to include the PTL clusters, these are the only production clusters that will be impacted.
      - name: PROD - AKS Auto Start
        run: ./scripts/aks/auto-start-stop.sh start production
        env:
          DEV_ENV: ${{ env.DEV_ENV }}

      - name: Untagged - AKS Auto Start
        run: ./scripts/aks/auto-start-stop.sh start untagged
        env:
          DEV_ENV: ${{ env.DEV_ENV }}

      - name: Output log file
        run: ./scripts/common/log-output.sh