Gitlabflow CD Action

Reusable GitHub Action for provisioning and destroying clusters, synchronizing releases, and updating project dependencies using RMK — with multi-cloud and multi-environment support.

What it does

This action encapsulates CD logic for tenant bootstrap repositories using RMK.
It supports a wide range of infrastructure and deployment operations, triggered by workflow inputs or environment settings.

Key features:

• Cluster provisioning
• Cluster destruction with optional [skip cluster destroy] support
• Release sync and version updates
• Project dependency version updates
• Helmfile validation
• Slack notifications (optional)
• AWS, Azure, GCP support via structured credentials

Supported commands

Controlled by the rmk_command input:

Command	Purpose
provision	Provision a cluster and sync releases
destroy	Tear down a cluster (with CAPI safety logic)
release_sync	Apply release definitions
release_update	Update release version/tag for a repository
project_update	Patch dependency version in project.yaml
helmfile_validate	Validate Helmfile templates

Why use this

Managing infra per repo is error-prone and hard to maintain. This action:

• Centralizes CD logic across all tenants and environments.
• Supports GitHub-native CD with workflow-level configuration.
• Tracks outputs for automation and audit.
• Minimizes boilerplate: run, pass inputs, and let RMK do the work.

Usage

Used in workflow_dispatch workflows inside tenant bootstrap repositories.

Example

name: Cluster provisioner

on:
  workflow_dispatch:
    inputs:
      rmk_command:
        description: 'Choose command: provision or destroy'
        required: true
        default: provision
        type: choice
        options:
          - provision
          - destroy
      rmk_version:
        description: RMK version
        required: false
        default: latest

env:
  RMK_CLUSTER_PROVIDER: aws

jobs:
  cluster-provision:
    runs-on: ubuntu-22.04
    steps:
      - name: Checkout
        uses: actions/checkout@v4
      
      - name: Run Gitlabflow CD Action
        uses: edenlabllc/gitlabflow.cd.action@v2
        with:
          github_token_repo_full_access: ${{ secrets.GH_TOKEN_REPO_FULL_ACCESS }}
          cluster_provider_credentials: ${{ secrets.CLUSTER_PROVIDER_CREDENTIALS }}
          rmk_cluster_provider: ${{ env.RMK_CLUSTER_PROVIDER }}
          rmk_command: ${{ inputs.rmk_command }}
          rmk_version: ${{ inputs.rmk_version }}

See examples/ for more templates.

Required secrets

Name	Purpose
GH_TOKEN_REPO_FULL_ACCESS	GitHub PAT with access to private repos
CLUSTER_PROVIDER_CREDENTIALS	JSON object with cloud credentials per env
SLACK_WEBHOOK	(Optional) Slack Incoming Webhook URL

Cluster provider credentials

See the action.yaml's cluster_provider_credentials section for more details.

Inputs

See the action.yaml's inputs section for more details.

Outputs

See the action.yaml's outputs section for more details.

Slack notifications

Enable by setting:

with:
  rmk_slack_notifications: true
  rmk_slack_webhook: ${{ secrets.SLACK_WEBHOOK }}
  rmk_slack_channel: "#rmk-test-cd"
  rmk_slack_message_details: |
    GitHub Actions Run: https://github.com/${{ github.repository }}/actions/runs/${{ github.run_id }}
    Triggered by: ${{ github.actor }}

Notifications are sent for Success, Failure, and Skip (e.g. [skip cluster destroy] in commit message).

Internals

• action.yml — defines action inputs and outputs.
• main.py — executes action logic.
• examples/ — example ready-to-use workflow templates.