Configure Terraform for Local Runs

At this early stage, all we want to do is ensure that terraform, when run locally, can initialize itself and run successfully but not manage any resources.

Copy and paste the following Terraform code into a new file, variables.tf, which declares the input variables we set up earlier in credentials.auto.tfvars

variable "github_admin_token" {
  type      = string
  sensitive = true
}

variable "github_ro_token" {
  type      = string
  sensitive = true
}

variable "tfe_token" {
  type      = string
  sensitive = true
}

Copy and paste the following Terraform code into a new file, terraform.tf, which will configure the Terraform Enterprise provider, AWS provider, and GitHub provider. Terraform will use local state files to keep track of any resources that it is managing.

terraform {
  required_providers {
    tfe = {
      source  = "hashicorp/tfe"
      version = "~> 0.49.2"
    }
    github = {
      source  = "integrations/github"
      version = "~> 5.39.0"
    }
  }

  required_version = "~> 1.6.0"
}

provider "tfe" {
  token = var.tfe_token
}

provider "github" {
  token = var.github_admin_token
}

Copy and paste the following into a new file, locals.tf, and adjust the values to match your desired Terraform Cloud and GitHub organization names:

locals {
  tfcloud_org_name        = "your_tfcloud_org_name"
  tfcloud_org_admin_email = "your_email_address"
  github_org_name         = "your_github_org_name"
}

Initialize Terraform:

$ terraform init

Initializing the backend...

Initializing provider plugins...
- Finding integrations/github versions matching "~> 5.39.0"...
- Finding hashicorp/tfe versions matching "~> 0.49.2"...
- Installing integrations/github v5.39.0...
- Installed integrations/github v5.39.0 (signed by a HashiCorp partner, key ID 38027F80D7FD5FB2)
- Installing hashicorp/tfe v0.49.2...
- Installed hashicorp/tfe v0.49.2 (signed by HashiCorp)

Partner and community providers are signed by their developers.
If you'd like to know more about provider signing, you can read about it here:
https://www.terraform.io/docs/cli/plugins/signing.html

Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

At this point, a terraform plan should succeed but show no resources need to change, somewhat obviously due to us not having asked it to manage any just yet:

$ terraform plan

No changes. Your infrastructure matches the configuration.

Terraform has compared your real infrastructure against your configuration and found no differences, so no changes are needed.