From 40f9bbe74b7333cb4d38132e93be08dbb0e4007b Mon Sep 17 00:00:00 2001 From: Ben Watson Date: Fri, 6 May 2022 10:50:36 -0400 Subject: [PATCH] updates the example version in the docs --- docs/index.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/index.md b/docs/index.md index 16fcfba7..53e20e39 100644 --- a/docs/index.md +++ b/docs/index.md @@ -10,7 +10,7 @@ Use the navigation to the left to read about the available resources. # Configure the ALKS Terraform Provider provider "alks" { url = "https://alks.foo.com/rest" - version = "~> 1.4.3" + version = ">= 2.2.0" } # Create an ALKS IAM role @@ -35,7 +35,7 @@ Static credentials can be provided via an `access_key`, `secret_key` and `token` ```hcl provider "alks" { url = "https://alks.foo.com/rest" - version = "~> 1.4.3" + version = ">= 2.2.0" access_key = "accesskey" secret_key = "secretkey" token = "sessiontoken" @@ -49,7 +49,7 @@ Terraform file: ```hcl provider "alks" { url = "https://alks.foo.com/rest" - version = "~> 1.4.3" + version = ">= 2.2.0" } ``` @@ -68,7 +68,7 @@ You can use an AWS credentials file to specify your credentials. The default loc ```hcl provider "alks" { url = "https://alks.foo.com/rest" - version = "~> 1.4.3" + version = ">= 2.2.0" shared_credentials_file = "/Users/my_user/.aws/credentials" profile = "foo" } @@ -86,7 +86,7 @@ Your ALKS provider block can look just like this: ```hcl provider "alks" { url = "https://alks.foo.com/rest" - version = "~> 1.4.3" + version = ">= 2.2.0" } ``` @@ -95,7 +95,7 @@ Since Machine Identities work with Instance Profile Metadata directly, it can be ```hcl provider "alks" { url = "https://alks.foo.com/rest" - version = "~> 1.4.3" + version = ">= 2.2.0" assume_role { role_arn = "arn:aws:iam::112233445566:role/acct-managed/JenkinsPRODAccountTrust" }