Update recommended Terraform provider versions

* Sync Terraform provider plugin versions to those used
internally
* Update mkdocs-material from v5.5.1 to v5.5.6
* Fix minor details in docs
This commit is contained in:
Dalton Hubble 2020-08-14 10:02:16 -07:00
parent c87db3ef37
commit 9a07f1d30b
9 changed files with 11 additions and 12 deletions

View File

@ -8,7 +8,7 @@ Notable changes between versions.
* Kubernetes [v1.18.8](https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.18.md#v1188) * Kubernetes [v1.18.8](https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.18.md#v1188)
* Migrate from Terraform v0.12.x to v0.13.x ([#804](https://github.com/poseidon/typhoon/pull/804)) (**action required**) * Migrate from Terraform v0.12.x to v0.13.x ([#804](https://github.com/poseidon/typhoon/pull/804)) (**action required**)
* Recommend Terraform v0.13.x ([migration guide](https://github.com/poseidon/typhoon/blob/5e70d7e2c8c71c37d9a0896a0945188f009011f9/docs/topics/maintenance.md#terraform-versions)) * Recommend Terraform v0.13.x ([migration guide](https://typhoon.psdn.io/topics/maintenance/#terraform-versions))
* Support automatic install of poseidon's provider plugins ([poseidon/ct](https://registry.terraform.io/providers/poseidon/ct/latest), [poseidon/matchbox](https://registry.terraform.io/providers/poseidon/matchbox/latest)) * Support automatic install of poseidon's provider plugins ([poseidon/ct](https://registry.terraform.io/providers/poseidon/ct/latest), [poseidon/matchbox](https://registry.terraform.io/providers/poseidon/matchbox/latest))
* Require Terraform v0.12.26+ (migration compatibility) * Require Terraform v0.12.26+ (migration compatibility)
* Require `terraform-provider-ct` v0.6.1 * Require `terraform-provider-ct` v0.6.1

View File

@ -55,7 +55,7 @@ terraform {
} }
aws = { aws = {
source = "hashicorp/aws" source = "hashicorp/aws"
version = "3.1.0" version = "3.2.0"
} }
} }
} }

View File

@ -52,7 +52,7 @@ terraform {
} }
azurerm = { azurerm = {
source = "hashicorp/azurerm" source = "hashicorp/azurerm"
version = "2.22.0" version = "2.23.0"
} }
} }
} }

View File

@ -56,7 +56,7 @@ terraform {
} }
google = { google = {
source = "hashicorp/google" source = "hashicorp/google"
version = "3.33.0" version = "3.34.0"
} }
} }
} }

View File

@ -55,7 +55,7 @@ terraform {
} }
aws = { aws = {
source = "hashicorp/aws" source = "hashicorp/aws"
version = "3.1.0" version = "3.2.0"
} }
} }
} }

View File

@ -52,7 +52,7 @@ terraform {
} }
azurerm = { azurerm = {
source = "hashicorp/azurerm" source = "hashicorp/azurerm"
version = "2.22.0" version = "2.23.0"
} }
} }
} }

View File

@ -56,7 +56,7 @@ terraform {
} }
google = { google = {
source = "hashicorp/google" source = "hashicorp/google"
version = "3.33.0" version = "3.34.0"
} }
} }
} }

View File

@ -154,8 +154,7 @@ $ tree ~/.terraform.d/
Update the version of the `ct` plugin in each Terraform working directory. Typhoon clusters managed in the working directory **must** be v1.12.2 or higher. Update the version of the `ct` plugin in each Terraform working directory. Typhoon clusters managed in the working directory **must** be v1.12.2 or higher.
``` ```tf
# providers.tf
provider "ct" { provider "ct" {
version = "0.6.1" version = "0.6.1"
} }
@ -211,7 +210,7 @@ Typhoon modules have been updated for v0.13.x, but retain compatibility with v0.
| Typhoon Release | Terraform version | | Typhoon Release | Terraform version |
|-------------------|---------------------| |-------------------|---------------------|
| v1.18.7 - ? | v0.12.26+, v0.13.x | | v1.18.8 - ? | v0.12.26+, v0.13.x |
| v1.15.0 - v1.18.8 | v0.12.x | | v1.15.0 - v1.18.8 | v0.12.x |
| v1.10.3 - v1.15.0 | v0.11.x | | v1.10.3 - v1.15.0 | v0.11.x |
| v1.9.2 - v1.10.2 | v0.10.4+ or v0.11.x | | v1.9.2 - v1.10.2 | v0.10.4+ or v0.11.x |
@ -228,7 +227,7 @@ An existing Terraform workspace may already manage earlier Typhoon clusters crea
First, upgrade `terraform-provider-ct` to v0.6.1 following the [guide](#upgrade-terraform-provider-ct) above. As usual, read about how `apply` affects existing cluster nodes when `ct` is upgraded. But `terraform-provider-ct` v0.6.1 is compatible with both Terraform v0.12 and v0.13, so do this first. First, upgrade `terraform-provider-ct` to v0.6.1 following the [guide](#upgrade-terraform-provider-ct) above. As usual, read about how `apply` affects existing cluster nodes when `ct` is upgraded. But `terraform-provider-ct` v0.6.1 is compatible with both Terraform v0.12 and v0.13, so do this first.
``` ```tf
provider "ct" { provider "ct" {
version = "0.6.1" version = "0.6.1"
} }

View File

@ -1,4 +1,4 @@
mkdocs==1.1.2 mkdocs==1.1.2
mkdocs-material==5.5.1 mkdocs-material==5.5.6
pygments==2.6.1 pygments==2.6.1
pymdown-extensions==7.1.0 pymdown-extensions==7.1.0