terraform-provider-iterative

terraform-provider-iterative copied to clipboard

Resources' read/create/delete operations should be deduplicated and carried in parallel when possible in order to speed up the user-facing operations. The only sane way of doing this is by representing the resources as a directed acyclic graph and walking it as Terraform does.

#423 doesn't log create/read/delete steps with the INFO level because they are being performed several times. Adding a <nil> check to avoid duplicate reads would allow us to move those logs back to the INFO level.

I sometimes still suffer the super long creation times for just two tasks. Very hard to reproduce

Takes me ~1min to apply and ~5min to destroy a minimal script single task with no workdir files to sync.

While this sounds reasonable, I think we need a long-term strategy fortpi in all its incarnations. Reimplementing terraform is not a path we want to go down.