Erik Osterman (CEO @ Cloud Posse)

@nitrocode why not just write: ``` components: abc: command: "terraform" ``` Then it should use your search path, and be compatible with tools like `asdf`

Yes, I could see that the PS1 maybe should be overridden to something plain like `(atmos) ue1-eks > ` so it's clear you're in the shell and for which particular...

Possibly, could you suggest your approach?

Good news, bad news. @rajhawaldar @nitrocode ## Bad News Bad news is, I think little can be done here, since we're just invoking a "login" (`-l`) shell based on `SHELL`....

@dudymas is looking into something like this on the side. No ETA.

Closing this since it's expected behavior. We should probably add a page to atmos docs like this: https://www.elastic.co/guide/en/beats/metricbeat/current/yaml-tips.html#avoid-leading-zeros

@Gowiem shared their experience here https://masterpoint.io/updates/opentofu-early-adopters/ TL;DR: Edit `atmos.yml` and set `terraform.command` to `tofu` (or whatever your binary is): ``` terraform: command: tofu ``` And if using our Spacelift components/integration,...


> updating to the latest version breaks all the scrolling on the site. To be clear, I'm not talking about `docusarus`, but `atmos` itself should emit a dialog like this...

Note, we did implement #312, which solves some of these things.