tfmigrate VS infracost-atlantis

https://github.com/future-architect/tftarget and https://github.com/minamijoyo/tfmigrate

I've seen tools such as https://github.com/minamijoyo/tfmigrate which looks like it'd work for existing deployments, however the piece I'm missing is how you'd manage to handle not running all the migrations when it is a new deployment, rather than an update of an existing deployment.

Interaction with Terraform Cloud can be achieved with the command-line interface (CLI), UI, API, or CI jobs. The remote or enhanced backend allows teams to run the Terraform binary from their laptops or a third-party CI job, but the operation is executed on a remote machine. This is especially useful for one-off administrative tasks like tainting or migrating resources – things that are not trivial with Atlantis and may require dedicated solutions like tfmigrate.

How about this approach? https://github.com/minamijoyo/tfmigrate

Flexibility is one of the core advantages of Atlantis, as it allows easy integration with other Terraform-helper tools(e.g., tfsec, checkov, Infracost, or Terratag). It can work with Terraform wrappers, such as Terragrunt, out of the box and even add some of Terragrunt’s features to vanilla Terraform – like before and after hooks for every execution stage (init, plan, apply, etc.).

Thanks! Those might have been the spinners (⠦) and tick (✔) symbols we use, using --log-level=info or the env INFRACOST_LOG_LEVEL=info switches them off. Did you end-up using the infracost-atlantis repo or roll your own? We updated that repo ~10 days ago to use infracost diff with Atlantis' $PLANFILE.