Erik Osterman (CEO @ Cloud Posse)

@haitham911 please resolve conflicts

@haitham911 please update the docs for `atmos terraform clean` https://atmos.tools/cli/commands/terraform/clean

> It looks like [goldmark](https://github.com/yuin/goldmark) does not yet support these alerts: > > - https://github.com/yuin/goldmark/discussions/422 > > We may still be able to support them in Glamour, though. Good catch!...

@suzuki-shunsuke > 1. Use a version manager like aqua My main concern is this: it defeats the purpose of the desired functionality, which is to avoid the need to manually...

So for a general purpose package manager, aqua is exceptional. For example, I like how we can define packages that install cleanly on a local workstation as well as in...

> For instance, when Atmos installs tflint, do you expect that users can execute `tflint` command directly? Tools like `aqua`, `tenv`, `asdf`, and many others follow a similar pattern. We're...

>> For instance, when Atmos installs tflint, do you expect that users can execute tflint command directly? > Probably you would expect this. Actually, no. While we could optimize for...

> Develop atmos-proxy like aqua-proxy https://github.com/suzuki-shunsuke/atmos-proxy - Not clear how the proxy would handle multiple concurrent versions of some tool installed (e.g. opentofu, helm, helmfile, etc) > Add the command...

@suzuki-shunsuke how would `atmos-proxy` get installed? I could understand if `atmos` could "cell-divide" so to say, but we don't want additional requirements to use atmos.

>> Links on Windows require administrative permissions > aqua uses hard links on Windows. > https://aquaproj.github.io/docs/reference/lazy-install#on-windows Without **Developer Mode**, my understanding is still that **Admin** is required. >> Not clear...