We encountered an issue after attempting to mgirate from apt-installed tools in Geodesic to Atmos Toolchain. Looking for insight into whether the toolchain introduces any environment variables that could affect workspace or backend configuration.
We source the toolchain on Geodesic startup:
if command -v atmos &>/dev/null; then
eval "$(atmos toolchain env --chdir / 2>/dev/null)" || true
fi
With this
atmos.yaml configuration addition:
toolchain:
file_path: ".tool-versions"
tools_dir: ".tools"
Local builds and Terraform operations work correctly but Spacelift workers fail across the board with this error:
│ Error: Backend configuration changed
│
│ A change in the backend configuration has been detected, which may require
│ migrating existing state.
│
│ If you wish to attempt automatic migration of the state, use "tofu init
│ -migrate-state".
│ If you wish to store the current configuration with no changes to the
│ state, use "tofu init -reconfigure".
Does Atmos Toolchain set any environment variables (e.g.,
TF_* or workspace-related) that could cause Terraform/OpenTofu to detect a backend change? I know this is a super broad question with lots of variables but curious if you had any recommendations
