terraform-provider-iterative
terraform-provider-iterative copied to clipboard
☁️ Terraform plugin for machine learning workloads: spot instance recovery & auto-termination | AWS, GCP, Azure, Kubernetes
Bumps [golang.org/x/net](https://github.com/golang/net) from 0.1.0 to 0.17.0. Commits b225e7c http2: limit maximum handler goroutines to MaxConcurrentStreams 88194ad go.mod: update golang.org/x dependencies 2b60a61 quic: fix several bugs in flow control accounting 73d82ef...
Hello, I encountered the following error while running a task with TPI: ``` │ Error: Plugin error │ │ with iterative_task.data-segmentation, │ on main.tf line 6, in resource "iterative_task" "data-segmentation":...
Script was `echo "Why me!?"` only: 
I'm not entirely sure if this is a bug or a feature, but it would be good to know in order to be able to automate actions based on the...
Bumps [github.com/hashicorp/go-getter](https://github.com/hashicorp/go-getter) from 1.6.2 to 1.7.0. Release notes Sourced from github.com/hashicorp/go-getter's releases. v1.7.0 What's Changed docs: provide logging recommendations by @mickael-hc in hashicorp/go-getter#371 Update aws sdk version by @Jukie in...
My OCD is triggered by the Failure of our release action: https://github.com/iterative/terraform-provider-iterative/actions/workflows/release.yml even though this isn't actually failing. We should update the [synchronize job](https://github.com/iterative/terraform-provider-iterative/blob/master/.github/workflows/release.yml#L40-L65) to work better or move it...
Adding `--cloud` & `--region` to all subsequent `leo` commands is annoying - is there a better UX? ([context](https://github.com/iterative/cml-examples-dev/pull/24#discussion_r1021996124))
[Terraform providers modules are named in such a way that prevents importing them](https://developer.hashicorp.com/terraform/plugin/sdkv2/best-practices/depending-on-providers#do-not-import-providers-as-go-modules). Now that we're going to use the `task` package from several repositories, we'll need to perform some...
Context: https://github.com/iterative/terraform-provider-iterative/pull/718#discussion_r1022858960 Older relate discussions: #344 Currently, string maps are allocated for each call of their respective cloud provider to determine the correct `machine_type` / `region` While previously the performance...
Context: https://github.com/iterative/terraform-provider-iterative/pull/718#discussion_r1022865596 Culprit: https://github.com/iterative/terraform-provider-iterative/blob/fd4a94041fcf5bab312699342fdbed39ae8ebcb9/iterative/gcp/provider.go#L441-L522 Ideally the solution is reuseable for parsing machine types for `runner` and `task`