Bootstrap Test Space

7min
Overview
Before any Terraform blueprint can be created, an API token to authorize interactions with the AutoCloud services and a test workspace module needs to be created to hold the Terraform source that will generate the blueprint.
Generate API Token
Navigate to the Terraform provider API token Service Accounts page in the AutoCloud settings UI.
Create a Service Account using CREATE and add Name, Description and assign it to a Group.
﻿
2. Generate a token for the Service Account using the ... menu, and set an expiration date. You will be allowed to copy it only once! To learn more about creating and using AutoCloud's Terraform Provider auth tokens, click here.
﻿
Bootstrap Test Module
Create a test module following the Hashicorp standard module structure, with additional files to configure providers:
Shell
❯ ls -1 .
LICENSE
README.md
main.tf
outputs.tf
providers.tf
variables.tf
versions.tf
❯ ls -1 .
LICENSE
README.md
main.tf
outputs.tf
providers.tf
variables.tf
versions.tf
﻿
Pin the required versions in versions.tf:
Terraform

terraform {
  required_version = ">= 1.0, < 1.6.0"

  required_providers {
    autocloud = {
      source  = "autoclouddev/autocloud"
      version = "0.13.0"
    }
  }
}

terraform {
  required_version = ">= 1.0, < 1.6.0"

  required_providers {
    autocloud = {
      source  = "autoclouddev/autocloud"
      version = "0.13.0"
    }
  }
}
﻿
Configure the AutoCloud provider in providers.tf:
Terraform
provider "autocloud" {
  ###
  # AutoCloud API Endpoint URL
  #
  # Sets the API endpoint that Terraform will talk to in order to determine state.
  #
  # export AUTOCLOUD_API=https://api.autocloud.io/api/v.0.0.1
  #
  # or via explicit configuration:

  # endpoint = "https://api.autocloud.io/api/v.0.0.1" # omit this, use autocloud prod for default



  ###
  # AutoCloud API Token
  #
  # Authorizes user to interact with AutoCloud API. These must be generated here:
  #
  # https://app.autocloud.io/settings/integrations/terraform-provider
  #
  # Value must be set either via environment variable:
  #
  # export AUTOCLOUD_TOKEN=
  #
  # or via explicit configuraiton:

  # token = ""
}

provider "autocloud" {
  ###
  # AutoCloud API Endpoint URL
  #
  # Sets the API endpoint that Terraform will talk to in order to determine state.
  #
  # export AUTOCLOUD_API=https://api.autocloud.io/api/v.0.0.1
  #
  # or via explicit configuration:

  # endpoint = "https://api.autocloud.io/api/v.0.0.1" # omit this, use autocloud prod for default



  ###
  # AutoCloud API Token
  #
  # Authorizes user to interact with AutoCloud API. These must be generated here:
  #
  # https://app.autocloud.io/settings/integrations/terraform-provider
  #
  # Value must be set either via environment variable:
  #
  # export AUTOCLOUD_TOKEN=
  #
  # or via explicit configuraiton:

  # token = ""
}
﻿
Add AutoCloud data source
Add an AutoCloud data source to main.tf:
Terraform
###
# Data Sources
data "autocloud_github_repos" "repos" {}

###
# Data Sources
data "autocloud_github_repos" "repos" {}
﻿
Initialize & Plan
Initialize Terraform:
Shell
❯ terraform init

Initializing the backend...

Initializing provider plugins...
- Finding autoclouddev/autocloud versions matching "0.13.0"...
- Using autoclouddev/autocloud v0.13.0 from the shared cache directory

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.

╷
│ Warning: Incomplete lock file information for providers
│
│ Due to your customized provider installation methods, Terraform was forced to calculate 
| lock file checksums locally for the following providers:
│   - autoclouddev/autocloud
│
│ The current .terraform.lock.hcl file only includes checksums for darwin_arm64, so 
| Terraform running on another platform will fail to install these providers.
│
│ To calculate additional checksums for another platform, run:
│   terraform providers lock -platform=linux_amd64
│ (where linux_amd64 is the platform to generate)
╵

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.
❯ terraform init

Initializing the backend...

Initializing provider plugins...
- Finding autoclouddev/autocloud versions matching "0.13.0"...
- Using autoclouddev/autocloud v0.13.0 from the shared cache directory

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.

╷
│ Warning: Incomplete lock file information for providers
│
│ Due to your customized provider installation methods, Terraform was forced to calculate 
| lock file checksums locally for the following providers:
│   - autoclouddev/autocloud
│
│ The current .terraform.lock.hcl file only includes checksums for darwin_arm64, so 
| Terraform running on another platform will fail to install these providers.
│
│ To calculate additional checksums for another platform, run:
│   terraform providers lock -platform=linux_amd64
│ (where linux_amd64 is the platform to generate)
╵

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.
﻿
Run the first plan:
Shell
❯ terraform plan
data.autocloud_github_repos.repos: Reading...
data.autocloud_github_repos.repos: Read complete after 1s [id=1676049391]

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.

❯ terraform plan
data.autocloud_github_repos.repos: Reading...
data.autocloud_github_repos.repos: Read complete after 1s [id=1676049391]

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.
﻿
﻿
Updated 26 Oct 2023
Did this page help you?
Writing Terraform Blueprints By Hand
Connect Terraform Modules
Docs powered by Archbee
TABLE OF CONTENTS
Overview
Generate API Token
Bootstrap Test Module
Add AutoCloud data source
Initialize & Plan