Stack validation failing in pipelines in Atmos `1.201.0`

[RoseSecurity]

Describe the Bug

Before kicking off our Spacelift pipelines, we validate all Atmos stacks in our GitHub Action pipelines. In Atmos 1.200.0 and prior versions, these actions succeeded with no issues. After upgrading to 1.201.0, our setup_and_validate step began to fail. Here is how to action is used:

jobs:
  setup_and_validate:
    runs-on: [self-hosted, Ubuntu, Common]
    env:
      ATMOS_CLI_CONFIG_PATH: ./rootfs/usr/local/etc/atmos
    outputs:
      atmos_version: ${{ steps.extract_atmos_version.outputs.atmos_version }}
    steps:
      - name: Checkout code
        uses: actions/checkout@ff7abcd0c3c05ccf6adc123a8cd1fd4fb30fb493 # https://github.com/actions/checkout/releases/tag/v4.2.2

      - name: Extract ATMOS_VERSION from Dockerfile
        id: extract_atmos_version
        run: |
          version=$(grep 'ARG ATMOS_VERSION=' Dockerfile | cut -d'=' -f2)
          echo "atmos_version=$version" >> "$GITHUB_OUTPUT"

      - name: Setup Atmos
        uses: cloudposse/github-action-setup-atmos@v2 # https://github.com/cloudposse/github-action-setup-atmos/releases
        with:
          atmos-version: ${{ steps.extract_atmos_version.outputs.atmos_version }}
          install-wrapper: false

      - name: Validate stacks
        run: atmos validate stacks

We checkout the code, extract the Atmos version from our Dockerfile, and install Atmos before running atmos validate stacks. After the upgrade, our pipeline logs show:

Run atmos validate stacks
##[debug]/usr/bin/bash -e /runner/_work/_temp/f4392d7f-d2e2-4657-9428-4e7650f1b5c0.sh



## Missing Configuration

The atmos.yaml CLI config file specifies the directory for Atmos stacks as stacks, but the directory does not exist.


## Getting Started

To configure and start using Atmos, refer to the following documents:

**Atmos CLI Configuration:** https://atmos.tools/cli/configuration

**Atmos Components:** https://atmos.tools/core-concepts/components

**Atmos Stacks:** https://atmos.tools/core-concepts/stacks

**Quick Start:** https://atmos.tools/quick-start
Error: Process completed with exit code 1.
##[debug]Finishing: Validate stacks

Expected Behavior

Here is the output when running Atmos 1.200.0 in the validation pipeline:

Setup:

Setup atmos version spec 1.200.0
Attempting to download 1.200.0...
Installing version v1.200.0 from GitHub
Acquiring v1.200.0 from https://github.com/cloudposse/atmos/releases/download/v1.200.0/atmos_1.200.0_linux_amd64
Installing downloaded file...
Successfully installed atmos from /runner/_work/_temp/27c56bf1-5203-4b77-892b-75fb1c83e785 to /runner/_work/_actions/cloudposse/github-action-setup-atmos/atmos/atmos
Successfully installed atmos to /runner/_work/_actions/cloudposse/github-action-setup-atmos/atmos
Cached version v1.200.0 for x64 in /opt/hostedtoolcache/atmos/1.200.0/x64
Successfully set up Atmos version 1.200.0 in /runner/_work/_actions/cloudposse/github-action-setup-atmos/atmos

Validation:

Run atmos validate stacks
  atmos validate stacks
  shell: /usr/bin/bash -e {0}
  env:
    ATMOS_CLI_CONFIG_PATH: ./rootfs/usr/local/etc/atmos
Validating Atmos Stacks...

✓ All stacks validated successfully

Steps to Reproduce

• Upgrade to Atmos 1.201.0
• Run validation pipelines

Screenshots

No response

Environment

• Self-hosted Ubuntu Github Action runners

Additional Context

No response

[aknysh]

@RoseSecurity thanks for reporting, we are looking into the issue and the fix will be in the next release