Database governance built for humans and agents — controlling changes and access across every major database.
Go cicddata-governancedata-maskingdata-securitydatabase-accessdatabase-governancedevopsdevsecopsflywaygitopsliquibasemongodbmysqloraclepostgresqlschema-migrationssecuritysql-clientsqlservertidb
chore(ci): start github-runner VM before triggering oncall sync (#20417)
Danny Xuc2eedec304a0
diff --git a/.github/workflows/trigger-oncall-sync.yml b/.github/workflows/trigger-oncall-sync.ymlindex e14de3c1cc..dedc865704 100644--- a/.github/workflows/trigger-oncall-sync.yml+++ b/.github/workflows/trigger-oncall-sync.yml@@ -16,6 +16,24 @@ jobs:dispatch:runs-on: ubuntu-24.04steps:+ - name: Authenticate to Google Cloud+ uses: google-github-actions/auth@v3+ with:+ credentials_json: ${{ secrets.GCP_SERVICE_ACCOUNT_KEY }}++ - name: Set up Cloud SDK+ uses: google-github-actions/setup-gcloud@v3++ - name: Start github-runner VM if stopped+ run: |+ STATUS=$(gcloud compute instances describe github-runner \+ --zone southamerica-east1-b --project bytebase-dev \+ --format='value(status)')+ if [ "$STATUS" != "RUNNING" ]; then+ gcloud compute instances start github-runner \+ --zone southamerica-east1-b --project bytebase-dev+ fi+- name: Trigger sync-oncall workflow on bytebase/oncallenv:GH_TOKEN: ${{ secrets.GHA_DISPATCH_TOKEN }}