Merge pull request #1764 from hashicorp/changelog-0point67

Prepping for v0.67.0 release

Author: Maed223

CHANGELOG.md

@@ -1,5 +1,7 @@
 ## Unreleased
 
+## v0.67.0
+
 ENHANCEMENTS:
 * `r/tfe_stack` Adds support for creating a Stack without specifying a VCS repo, by @sujaysamanta [#1760](https://github.com/hashicorp/terraform-provider-tfe/pull/1760)
 

README.md

@@ -28,7 +28,7 @@ Declare the provider in your configuration and `terraform init` will automatical
 terraform {
   required_providers {
     tfe = {
-      version = "~> 0.64.0"
+      version = "~> 0.67.0"
     }
   }
 }
@@ -44,7 +44,7 @@ The above snippet using `required_providers` is for Terraform 0.13+; if you are
 
 ```hcl
 provider "tfe" {
-  version = "~> 0.64.0"
+  version = "~> 0.67.0"
   ...
 }
 ```

version/VERSION

@@ -1 +1 @@
-0.66.0
+0.67.0

website/docs/index.html.markdown

@@ -8,7 +8,7 @@ description: |-
 # HCP Terraform and Terraform Enterprise Provider
 
 This provider is used to interact with the many resources supported by
-[HCP Terraform](/docs/cloud/index.html).  As [Terraform
+[HCP Terraform](/docs/cloud/index.html). As [Terraform
 Enterprise](/docs/enterprise/index.html) is a self-hosted distribution of
 HCP Terraform, this provider supports both Cloud and Enterprise.
 
@@ -30,7 +30,7 @@ token](/docs/cloud/users-teams-organizations/api-tokens.html) from an account
 with appropriate permissions. This user should belong to the "owners" team of
 every organization you wish to manage. Alternatively, you can use [an organization or team
 token](/docs/cloud/users-teams-organizations/api-tokens.html) instead of a user
-token, but it will limit which resources you can manage.  Organization and team
+token, but it will limit which resources you can manage. Organization and team
 tokens cannot manage resources across multiple organizations, and organization
 tokens cannot manage certain resource types (like SSH keys). See the [API token
 documentation](/docs/cloud/users-teams-organizations/api-tokens.html#access-levels)
@@ -39,10 +39,10 @@ for more details about access to specific resources.
 There are several ways to provide the required token:
 
 - **Set the `token` argument in the provider configuration.** You can set
-the `token` argument in the provider configuration.  Use an input variable for
-the token.
+  the `token` argument in the provider configuration. Use an input variable for
+  the token.
 - **Set the `TFE_TOKEN` environment variable:** The provider can read the
-`TFE_TOKEN` environment variable and the token stored there to authenticate.
+  `TFE_TOKEN` environment variable and the token stored there to authenticate.
 
 When configuring the input variable for either of these options, mark them as sensitive.
 
@@ -56,14 +56,13 @@ If you are using this provider on your local command line without remote operati
 are two more options available to you:
 
 - **Use `terraform login` to generate credentials:** When using this provider with
-Terraform on your local command line, it can automatically discover the credentials generated by
-[`terraform login`](https://developer.hashicorp.com/terraform/cli/commands/login).
+  Terraform on your local command line, it can automatically discover the credentials generated by
+  [`terraform login`](https://developer.hashicorp.com/terraform/cli/commands/login).
 - **Set a `credentials` block in your CLI config file (.terraformrc):** See
-the [CLI Configuration File documentation](/docs/commands/cli-config.html).
-If you used the `TF_CLI_CONFIG_FILE` environment variable to specify a
-non-default location for .terraformrc, the provider will also use that location.
-Using a `credentials_helper` block is not supported.
-
+  the [CLI Configuration File documentation](/docs/commands/cli-config.html).
+  If you used the `TF_CLI_CONFIG_FILE` environment variable to specify a
+  non-default location for .terraformrc, the provider will also use that location.
+  Using a `credentials_helper` block is not supported.
 
 ## Versions
 
@@ -75,7 +74,7 @@ automatically installed by `terraform init` in the future:
 terraform {
   required_providers {
     tfe = {
-      version = "~> 0.64.0"
+      version = "~> 0.67.0"
     }
   }
 }
@@ -88,7 +87,7 @@ The above snippet using `required_providers` is for Terraform 0.13+; if you are
 
 ```hcl
 provider "tfe" {
-  version = "~> 0.64.0"
+  version = "~> 0.67.0"
   ...
 }
 ```
@@ -101,7 +100,7 @@ For more information on provider installation and constraining provider versions
 provider "tfe" {
   hostname = var.hostname # Optional, defaults to HCP Terraform `app.terraform.io`
   token    = var.token
-  version  = "~> 0.64.0"
+  version  = "~> 0.67.0"
 }
 
 # Create an organization
@@ -114,15 +113,15 @@ resource "tfe_organization" "org" {
 
 The following arguments are supported:
 
-* `hostname` - (Optional) The HCP Terraform or Terraform Enterprise hostname to connect to.
+- `hostname` - (Optional) The HCP Terraform or Terraform Enterprise hostname to connect to.
   Defaults to `app.terraform.io`. Can be overridden by setting the
   `TFE_HOSTNAME` environment variable.
-* `token` - (Optional) The token used to authenticate with HCP Terraform or Terraform Enterprise.
+- `token` - (Optional) The token used to authenticate with HCP Terraform or Terraform Enterprise.
   See [Authentication](#authentication) above for more information.
-* `ssl_skip_verify` - (Optional) Whether or not to skip certificate verifications.
+- `ssl_skip_verify` - (Optional) Whether or not to skip certificate verifications.
   Defaults to `false`. Can be overridden setting the `TFE_SSL_SKIP_VERIFY`
   environment variable.
-* `organization` - (Optional) The default organization that resources should
+- `organization` - (Optional) The default organization that resources should
   belong to. If provided, it's usually possible to omit resource-specific `organization`
   arguments. Ensure that the organization already exists prior to using this argument.
   This can also be specified using the `TFE_ORGANIZATION` environment variable.