[vitalysh]

Just wondering here, but why would you use this vs terraform? Given that I can define most of the stuff I need from AWS in terraform and check the state of the infra via plan command, what would be the use case for CLI? I'm actively trying to break the habit of modifying infra without first writing terraform document for it. This way I can always be sure that I have no surprises when creating a new environment.

[solidsnack9000]

There is no state file and it is a more "AWS first" way to do queries and one off tasks. Especially for destroying old stuff, there is a value in a non-idempotent approach.

[skywhopper]

Terraform can't tell you about the stuff it doesn't know about.

[vitalysh]

And this is exactly what I'm trying to avoid. Terraform should know about most of the stuff.

[manojlds]

Data sources in TF are sort of that. But I get what you mean.

[dkarapetyan]

How complicated have your terraform templates been? Because it gets pretty hairy pretty fast because not everything fits the declarative terraform model.

[vitalysh]

I can see that templates can get complex pretty fast, but so far we manage it. Big benefit we have - a fresh start with infra about a year ago.

[djschnei]

Wondering the same... not seeing it...