@Erik Osterman (Cloud Posse) https://github.com/cloudposse/atmos/pull/1868

can you give me the TL;DR? I'm having trouble understanding the PR description

the PR https://github.com/cloudposse/atmos/pull/1774 introduced a regressing: when using

ATMOS_CLI_CONFIG_PATH

to specify the path to

atmos.yaml

(e.g. in GH actions),

stacks

or

components/terraform

were incorrectly resolved relative to the

ATMOS_CLI_CONFIG_PATH

directory instead of the current working directory. If Atmos commands are executed from a working directory, but

atmos.yaml

was in different directory (e.g. in

/rootfs/usr/local/etc/atmos/atmos.yaml

), Atmos tried to resolve the stacks relative to

/rootfs/usr/local/etc/atmos/atmos.yaml

and could not find it

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

That sounds wrong to me. The default base-path is the dirname("path to atmos.yaml"). The stacks are relative to the base-path. "instead of the current working directory" this is the part that sounds wrong to me