Erik Osterman (CEO @ Cloud Posse)

@suzuki-shunsuke I neglected to respond to this comment. This is a good one, because it highlights the strategic differences of what we're optimizing for in atmos vs aqua. As you...

One more idea, symlinks can be an optional optimization, if it causes problems.

Based on this, I'm concerned we haven't captured the requirement that within a project, multiple tool versions must be supported. Different versions of terraform components can require different versions of...

> [!WARNING] > # ⚠ Draft Proposal (still working on it) > I will remove this 👆 when proposal finished. ## General Requirements ### Must: - Install packages on-demand when...

Aha, such as in one component creates specific artifacts that should get cleaned up. This would be in: ```yaml components: terraform: foobar: settings: terraform.clean.paths: - foo.txt vars: ... ```

> pipeform is interesting, but honestly I'm not sure if we should really use this by default. I tried pipeform a bit. When we use pipeform, the plan result doesn't...

@suzuki-shunsuke here is what I am referring to. Are we talking about the same thing? 

@suzuki-shunsuke if the objective is to also support the regular terraform output, I think that could still be accomplished. ``` # github_issue_label.fooo will be created + resource "github_issue_label" "fooo" {...

> We need to discuss these problems with pipeform's maintainers. I'll get the conversation started by opening an issue in the project and linking to this topic.

@suzuki-shunsuke the terraform plan handling was just resolved in: - magodo/pipeform#10