Anyone experience this issue, we are currently testing a new feature of describe-affected in atmos version

1.206.0-rc.4

, coming from version

1.198.0

and experiencing errors with base path. Tried to follow the documentation of updated Base_paths in newer versions, https://atmos.tools/changelog/base-path-behavior-change. and also tried with following env variables per documentation

ATMOS_CLI_CONFIG_PATH: "./config", ATMOS_BASE_PATH: ".." && ATMOS_BASE_PATH: ""

. Running in GitHub Workflows and atmos.yaml is located in SubDirectory called Config in a Git Root Directory ( which is

git-iac-repo

from below error ). Relative Paths for the Components and Stacks from the runner are, Components:

/__w/git-iac-repo/git-iac-repo/components/terraform

Stacks:

/__w/git-iac-repo/git-iac-repo/stacks

@PePe Amengual

# Error 
 
**Error:** directory for Atmos stacks does not exist 
 
## Hints 
 
:bulb: Stacks directory not found: /__w/git-iac-repo/stacks 
# Error 
 
**Error:** directory for Atmos stacks does not exist 
 
## Hints 
 
:bulb: Stacks directory not found: /__w/git-iac-repo/stacks 
Error appears 
Run if [[ -f "/__w/git-iac-repo/git-iac-repo/components/terraform/applicationgateway/stg-wus3-appgateway_be-aa699e0682be123e8c1a5beb008662e6b476ad12.planfile" ]]; then 
Run if [[ "false" == "true" ]]; then 
/__w/git-iac-repo/git-iac-repo/metadata/step-summary-stg-wus3-appgateway_be.md found 
Drift detection mode disabled 
Run echo "rand=$(openssl rand -hex 5)" >> "$GITHUB_OUTPUT"

@Girish Maddineni please create a GH issue with this description, we'll look into it ASAP

Also, consider using

ATMOS_CHDIR

instead of

ATMOS_CLI_CONFIG_PATH

and

ATMOS_BASE_PATH

; everything gets so much easier if you're not fighting the defaults inside of Atmos. Not saying there's anything wrong with it, and these definitely work, but it increases the cognitive load the more environment variables you need to set. Using atmos chdir, Atmos executes a change directory prior to running any command.

but ATMOS_CHDIR will "cd" in a directory? so if we have in the root /stacks and /components but the /config/atmos.yaml how would that look like?

everything gets so much easier if you're not fighting the defaults inside of Atmos.

That's why I added this line 😃