diff --git a/README.md b/README.md index 4240096e..1acf7943 100644 --- a/README.md +++ b/README.md @@ -21,7 +21,7 @@ This module is used for creating IAM Roles via the ALKS API. For example on macOS: ``` -curl -L https://github.com/Cox-Automotive/terraform-provider-alks/releases/download/1.3.0/terraform-provider-alks-darwin-amd64.tar.gz | tar zxv +curl -L https://github.com/Cox-Automotive/terraform-provider-alks/releases/download/1.4.2/terraform-provider-alks-darwin-amd64.tar.gz | tar zxv ``` * Configure Terraform to use this plugin by placing the binary in `.terraform.d/plugins/` on MacOS/Linux or `terraform.d\plugins\` in your user's "Application Data" directory on Windows. @@ -41,7 +41,7 @@ Static credentials can be provided via an `access_key`, `secret_key` and `token` ```tf provider "alks" { url = "https://alks.foo.com/rest" - version = "~> 1.3.0" + version = "~> 1.4.0" access_key = "accesskey" secret_key = "secretkey" token = "sessiontoken" @@ -55,7 +55,7 @@ You can provide your credentials via the `AWS_ACCESS_KEY_ID`, `AWS_SECRET_ACCESS ```tf provider "alks" { url = "https://alks.foo.com/rest" - version = "~> 1.3.0" + version = "~> 1.4.0" } ``` @@ -74,7 +74,7 @@ You can use an AWS credentials file to specify your credentials. The default loc ```tf provider "alks" { url = "https://alks.foo.com/rest" - version = "~> 1.3.0" + version = "~> 1.4.0" shared_credentials_file = "/Users/brianantonelli/.aws/credentials" profile = "foo" } @@ -93,7 +93,7 @@ Your ALKS provider block can look just like this: ```tf provider "alks" { url = "https://alks.foo.com/rest" - version = "~> 1.3.0" + version = "~> 1.4.0" } ``` @@ -102,7 +102,7 @@ Since Machine Identities work with Instance Profile Metadata directly, it can be ```tf provider "alks" { url = "https://alks.foo.com/rest" - version = "~> 1.3.0" + version = "~> 1.4.0" assume_role { role_arn = "arn:aws:iam::112233445566:role/acct-managed/JenkinsPRODAccountTrust" }