Casper da Costa-Luis
Casper da Costa-Luis
related: #461
Well even though implementation would need to be done in [TPI](https://github.com/iterative/terraform-provider-iterative), it would also need exposure in CML as well (unless we make it default behaviour).
images could handle formatting but I'm not sure whether that would be enough - surely the underlying filesystem needs to support it (i.e. be block-like)?
Added an item to ~the `p1` checklist here~ #397 instead :)
thx added to #450 :)
Already done https://registry.terraform.io/providers/iterative/iterative/latest/docs/guides/getting-started#debugging
potentially could transfer this to [tpi](https://github.com/iterative/tpi)?
To summarise DVC-required features of TPI `task`: - [x] serverless (no SaaS deps) - [x] multi-cloud provisioning support - [x] sync via folder - [ ] sync directly (e.g. via...
- is `if: always()` or equivalent supported in all CIs? - the extra bulkiness sounds fine provided it's optional-to-fix-edge-cases rather than default-required - in any case a `cml runner gc...
yes it is. - efficiency (try to sync diffs rather than entire files) - workspace awareness (skip uploading `.git/`, `.terraform*` etc.)