#spacelift - February 2025

Hello,
We have got an issue after this update https://github.com/cloudposse/github-action-atmos-affected-trigger-spacelift/pull/48/files.

The github-action-atmos-affected-trigger-spacelift GHA fails to trigger the affected Spacelift stacks.

Any ideas how to quickly fix it ?

The GHA config:

name: "Deploy Affected Spacelift Stacks"

on:
  pull_request:
    types: [closed]
    branches:
      - main

jobs:
  run:
    if: github.event.pull_request.merged == true
    runs-on:
      group: vnext
    steps:
      - name: Atmos Affected Stacks Trigger Spacelift
        uses: cloudposse/github-action-atmos-affected-trigger-spacelift@v2
        with:
          atmos-config-path: ./rootfs/usr/local/etc/atmos
          deploy: true
          github-token: ${{ secrets.GITHUB_TOKEN }}
          head-ref: ${{ github.sha }}~1
          install-jq: true
          jq-version: 1.7
          atmos-version: 1.153.0

Error:

If anyone is interested, I’ve submitted a feature request to Spacelift to add Atmos as a vendor for stack creation. You can vote for it here: https://feedback.spacelift.io/p/incorporating-atmos-into-stack-creation.

Another feature request, can we just eliminate the need to separately create stacks? Drive stack config and runs entirely from source...
https://feedback.spacelift.io/p/drive-a-run-entirely-from-runtime-configuration-no-stack-required