kubespray/contrib/terraform/metal/versions.tf


terraform {
  required_version = ">= 0.12"
  required_providers {
    metal = {
      source = "equinix/metal"
    }
  }
}
Terraform dynamic inventory 0.12.12 (#5298) * Update parsing of terraform state file for 0.12.12 * Resource does not seem to have a module element but instead has provider * Return the boolean right way if it is already a bool since a bool does not have an lower method * Remove the setting of ansible_ssh_user to root for all Packet Not all servers in packet are accessed as root by default. CoreOS systems use the `core` user. Removing this allows the user to specify the remote user with an extra_var or in an ansible.cfg file. * Default to root user for packet devices except on CoreOS * Update TF_VERSION for packet in tf-validate-packet Update TV_VERSION to 0.12.12 for gitlab-ci tf-validate-packet tests * convert packet terraform files to TV_VERSION 4 * initalize terraform before copying the variable file to the top level dir 2019-10-29 15:02:42 +08:00
			`terraform {`
			`required_version = ">= 0.12"`
Fix terraform0.13 errors (#7077) * [terraform/aws] Fix Terraform >=0.13 warnings Terraform >=0.13 gives the following warning: ``` Warning: Interpolation-only expressions are deprecated ``` The fix was tested as follows: ``` rm -rf .terraform && terraform0.12.26 init && terraform0.12.26 validate rm -rf .terraform && terraform0.13.5 init && terraform0.13.5 validate rm -rf .terraform && terraform0.14.3 init && terraform0.14.3 validate ``` which gave no errors nor warnings. * [terraform/openstack] Fixes for Terraform >=0.13 Terraform >=0.13 gives the following error: ``` Error: Failed to install providers Could not find required providers, but found possible alternatives: hashicorp/openstack -> terraform-provider-openstack/openstack ``` This patch fixes these errors. This fix was tested as follows: ``` rm -rf .terraform && terraform0.12.26 init && terraform0.12.26 validate rm -rf .terraform && terraform0.13.5 init && terraform0.13.5 validate rm -rf .terraform && terraform0.14.3 init && terraform0.14.3 validate ``` which gave no errors nor warnings for Terraform 0.13.5 and Terraform 0.14.3. Unfortunately, 0.12.x gives a harmless warning, but with 0.14.3 out the door, I guess we need to move on. * [terraform/packet] Fixes for Terraform >=0.13 This fix was tested as follows: ``` export PACKET_AUTH_TOKEN=blah-blah rm -rf .terraform && terraform0.12.26 init && terraform0.12.26 validate rm -rf .terraform && terraform0.13.5 init && terraform0.13.5 validate rm -rf .terraform && terraform0.14.3 init && terraform0.14.3 validate ``` Errors are gone, but warnings still remain. It is impossible to please all three versions of Terraform. * Add tests for Terraform >=0.13 2020-12-23 21:08:26 +08:00			`required_providers {`
[terraform] use modern day equinix metal provider (#8748) * [terraform] use modern day equinix metal provider * [CI] ensure packet job tests metal 2022-04-28 01:34:13 +08:00			`metal = {`
			`source = "equinix/metal"`
Fix terraform0.13 errors (#7077) * [terraform/aws] Fix Terraform >=0.13 warnings Terraform >=0.13 gives the following warning: ``` Warning: Interpolation-only expressions are deprecated ``` The fix was tested as follows: ``` rm -rf .terraform && terraform0.12.26 init && terraform0.12.26 validate rm -rf .terraform && terraform0.13.5 init && terraform0.13.5 validate rm -rf .terraform && terraform0.14.3 init && terraform0.14.3 validate ``` which gave no errors nor warnings. * [terraform/openstack] Fixes for Terraform >=0.13 Terraform >=0.13 gives the following error: ``` Error: Failed to install providers Could not find required providers, but found possible alternatives: hashicorp/openstack -> terraform-provider-openstack/openstack ``` This patch fixes these errors. This fix was tested as follows: ``` rm -rf .terraform && terraform0.12.26 init && terraform0.12.26 validate rm -rf .terraform && terraform0.13.5 init && terraform0.13.5 validate rm -rf .terraform && terraform0.14.3 init && terraform0.14.3 validate ``` which gave no errors nor warnings for Terraform 0.13.5 and Terraform 0.14.3. Unfortunately, 0.12.x gives a harmless warning, but with 0.14.3 out the door, I guess we need to move on. * [terraform/packet] Fixes for Terraform >=0.13 This fix was tested as follows: ``` export PACKET_AUTH_TOKEN=blah-blah rm -rf .terraform && terraform0.12.26 init && terraform0.12.26 validate rm -rf .terraform && terraform0.13.5 init && terraform0.13.5 validate rm -rf .terraform && terraform0.14.3 init && terraform0.14.3 validate ``` Errors are gone, but warnings still remain. It is impossible to please all three versions of Terraform. * Add tests for Terraform >=0.13 2020-12-23 21:08:26 +08:00			`}`
			`}`
Terraform dynamic inventory 0.12.12 (#5298) * Update parsing of terraform state file for 0.12.12 * Resource does not seem to have a module element but instead has provider * Return the boolean right way if it is already a bool since a bool does not have an lower method * Remove the setting of ansible_ssh_user to root for all Packet Not all servers in packet are accessed as root by default. CoreOS systems use the `core` user. Removing this allows the user to specify the remote user with an extra_var or in an ansible.cfg file. * Default to root user for packet devices except on CoreOS * Update TF_VERSION for packet in tf-validate-packet Update TV_VERSION to 0.12.12 for gitlab-ci tf-validate-packet tests * convert packet terraform files to TV_VERSION 4 * initalize terraform before copying the variable file to the top level dir 2019-10-29 15:02:42 +08:00			`}`