Files
vitor-aignosi 7f60aeefef Point deploy workflow at laborious-legacy-worker release
- Deploy the repo as its own opt-in release, laborious-legacy-worker, a
  single Deployment with RUNTIME=legacy, instead of the legacy runtime
  of laborious-worker. New code now lives in sientia-dataops-laborious.
- Set project_name to laborious-legacy so the Gitea mirror target
  resolves to gitea_admin/sientia-dataops-laborious-legacy.
- Bump GITHUB_BRANCH in the chart base .env and the gcp profile .env
  rather than the old .runtimes.legacy.env path.
- Rename the Sonar project to sientia-dataops-laborious-legacy.
2026-10-09 10:19:45 -03:00

39 lines
1.4 KiB
YAML

name: Deploy DataOps Worker
on:
pull_request:
types: [closed]
branches: [main, 'release/**', 'feature/**']
workflow_dispatch:
permissions:
contents: write
id-token: write
pull-requests: read
jobs:
deploy:
name: Deploy
if: github.event_name == 'workflow_dispatch' || github.event.pull_request.merged == true
uses: Aignosi/github_workflow_templates/.github/workflows/reusable-deploy-dataops.yml@main
with:
branch_name: ${{ github.event.pull_request.head.ref }}
project_name: 'laborious-legacy'
# This repo deploys its own opt-in release, laborious-legacy-worker: a single Deployment
# (no runtimes map, like scouter-worker/orchestrator-worker) with RUNTIME=legacy as the
# queue suffix. The new code lives in sientia-dataops-laborious (release laborious-worker).
# The Gitea mirror target is derived from this repo's name:
# gitea_admin/sientia-dataops-laborious-legacy. GITHUB_BRANCH is bumped in the chart base
# .env (release is opt-in; air-gapped profiles pin their own version) and in the gcp
# profile's laborious-legacy-worker.env.
chart_name: 'laborious-legacy-worker'
env_list_path: '[".env"]'
profile: 'gcp'
profile_env_list_path: '[".env"]'
update_version_in: '["pyproject"]'
create_tarball: ${{ github.event_name == 'pull_request' }}
mirror: true
bump_chart: true
deploy: true
secrets: inherit