Figure out how we should use Terraform v0.15 about compliantkubernetes

[tordsson]

Terraform v0.14 likely has quite some time until end of life, but an early investigation on how to (migrate?, support both versions?) would be very useful. @simonklb: your input on this would be great

[simonklb]

Terraform v0.14 likely has quite some time until end of life, but an early investigation on how to (migrate?, support both versions?) would be very useful. @simonklb: your input on this would be great

Both versions should be supported by ck8s-devbox. I've tried upgrading to Terraform 0.15 and terraform plan runs successfully and the diff is empty on the following providers (just had to make a few changes upstream to the aws module which used a deprecated function):

providers="aws citycloud exoscale safespring"

for provider in $providers; do
    CK8S_CLOUD_PROVIDER=$provider
    CK8S_CONFIG_PATH=~/.ck8s/simon-$provider-kubespray

    ck8s-devbox ck8s-terraform apply sc
done

docker build -t ck8s-devbox --build-arg TERRAFORM_VERSION=0.15.4 .

for provider in $providers; do
    CK8S_CLOUD_PROVIDER=$provider
    CK8S_CONFIG_PATH=~/.ck8s/simon-$provider-kubespray

    ck8s-devbox ck8s-terraform plan sc
done

* `terraform init` and `terraform apply` leave the `compliantkubernetes-kubespray` and `kubespray` untouched, i.e., without dirty files.

This isn't currently possible. You can set TF_DATA_DIR to move the .terraform directory, but the provider dependency lock file path is currently hardcoded.
https://github.com/hashicorp/terraform/blob/ffe056bacb9f2cf403fa3b6b894c5fbe1fa850a7/internal/command/meta_dependencies.go#L10-L28

[cristiklein]

I just tested and you are right. ck8s-terraform plan cksc works well, both within and outside the container. Outside the container, one needs to run ck8s-terraform-init which dirties the git repo, but that's something we need to live with.

Anyway, if there are no greater issues, then we are in good shape to switch to TF 0.15.0.

Please close this issue.