Hi! Quick question about Atmos config setup. In our repo we currently have two copies of `atmos.yaml`: • one at the repo root (

devops/atmos.yaml

) • another baked into our container image at

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

Right now these two files are 1:1 identical (I diffed them). In CI, our GitHub workflows pass

atmos-config-path: ${{ vars.ATMOS_CONFIG_PATH }}

, so Atmos should be using the config file from the checked-out repo. I’d like to simplify this and move to a single

atmos.yaml

as the source of truth. Is it safe (and idiomatic in CloudPosse setups) to: • keep only the root

atmos.yaml

, • have the Docker image copy that file into

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

, and point CI (ATMOS_CONFIG_PATH) at the root file? Or do you recommend keeping a separate, baked-in config for the image in addition to the repo one? Any best-practice guidance (and pitfalls to avoid) would be really appreciated.

atmos.yaml

at the repo root is enought

Yes, keep one at the root

Thanks, appreciate! I am going to give Native CI a try soon! 😄