Open lilatomic opened 5 months ago
some way of ejecting from pants, so you can run manual steps. For example, sometimes you'll need to upgrade state or migrate backends (which has come up a few times). There are also importing resources and inspecting state. Pants doesn't have to have knobs for all of these, but can help in many ways (such as pants export mapping to terraform init; or pants run trying to pass in vars files)
See https://github.com/pantsbuild/pants/pull/13023 for a PR which would have added a tf-run
goal to invoke Terraform with specified arguments.
the TF backend is currently really slow because it doesn't cache providers
Are the provider downloaded to the sandbox currently? If so, can Terraform be configured to cache them elsewhere?
https://developer.hashicorp.com/terraform/cli/config/config-file#provider-plugin-cache seems relevant for configuring a shared Terraform plugin cache.
Terraform is nearing being ready for a release from
experimental
. That will mean that we have all the functionality in place to provide a stable user frontend and decent user experience. There are things left to do:download-terraform
->terraform
. Probably do as we exit experimental since it too will be a breaking changepants export
mapping toterraform init
; orpants run
trying to pass in vars files)terraform init
, and that's technically required and always valid. But it does mean that changes which don't affect the required providers still cause us to reinitialise terraform which takes a wileexperimental_deploy
able things?