[Terraform] CDKTF module apply

DONT FORGOT aws configurebefore do something!!!

Use PreBuilt

• CDKTF prebuilt bindings for hashicorp/aws provider

  • Typescript

  • Python

  • Java

  • C#

  • Go

Use Terraform Module on CDKTF

• Approach 1 - visit github ('Terraform AWS modules' github)

• Approach 2 - visit Terraform registry

and pick what you need.

Provider Setup

let's begin with AWS provider setup

you can see name, source

put that info in cdktf.json

and type

$ cdktf get

after that, you can see .gendirectory, and able to import aws modules.

But it's just begun! It's not a module! It's a provider! Keep bare with this document

About Versioning Option

There are several version constraint operators you can use in Terraform and package management systems. Here are the most common options:

1. Exact version: "= 3.0.0" - Only use exactly version 3.0.0

2. Greater than: "> 3.0.0" - Use any version greater than 3.0.0

3. Greater than or equal to: ">= 3.0.0" - Use version 3.0.0 or any greater version

4. Less than: "< 4.0.0" - Use any version less than 4.0.0

5. Less than or equal to: "<= 3.9.9" - Use any version up to and including 3.9.9

6. Pessimistic constraint (allows only patch updates): "~> 3.0.0" - Use versions from 3.0.0 up to, but not including, 3.1.0

7. Pessimistic constraint (allows minor and patch updates): "~> 3.0" - Use versions from 3.0.0 up to, but not including, 4.0.0

8. Range constraint: ">= 3.0, < 4.0" - Use any version from 3.0.0 up to, but not including, 4.0.0

9. Wildcard constraints: "3.*" or "3.x" - Any version in the 3.x series

10. Any version: "*" or omitting the version - Use the latest version available

11. Combination: You can combine these for more specific ranges, e.g., ">= 3.0, < 3.5"

When choosing a version constraint, consider:

• How stable you need your infrastructure to be

• How often you want to manually update and test new versions

• The module's update frequency and backwards compatibility promises

For most cases, the pessimistic constraint (~>) offers a good balance between getting updates and maintaining stability. However, for critical infrastructure, you might want to pin to an exact version and update manually after thorough testing.

Import modules

this time, we will import vpc module.

and add this info on cdktf.json

and run cdktf getthen you can see module.

add something like this on cdktf.json

  "language": "typescript",
  "app": "npx ts-node cdktf-main.ts",
  "projectId": "00000000-0000-0000-0000-000000000000",
  "sendCrashReports": "false",
  "terraformProviders": [
    "aws@~> 4.0"
  ],
  "terraformModules": [
    {
      "name": "vpc",
      "source": "terraform-aws-modules/vpc/aws",
      "version": "~> 5.0"
    }
  ],
  "context": {
    "excludeStackIdFromLogicalIds": "true",
    "allowSepCharsInLogicalIds": "true"
  }
}

and run cdktf get

Commands:
  cdktf init [OPTIONS]                Create a new cdktf project from a template.
  cdktf get [OPTIONS]                 Generate CDK Constructs for Terraform providers and modules.
  cdktf convert [OPTIONS]             Converts a single file of HCL configuration to CDK for Terraform. Takes the file to be converted on stdin.
  cdktf deploy [OPTIONS] <stacks..>   Deploy the given stacks                                                                                                                                    [aliases: apply]
  cdktf destroy [OPTIONS] <stacks..>  Destroy the given stacks
  cdktf diff [stack] [OPTIONS]        Perform a diff (terraform plan) for the given stack                                                                                                         [aliases: plan]
  cdktf list [OPTIONS]                List stacks in app.
  cdktf login                         Retrieves an API token to connect to Terraform Cloud.
  cdktf synth [stack] [OPTIONS]       Synthesizes Terraform code for the given app in a directory.                                                                                          [aliases: synthesize]
  cdktf watch [stack] [OPTIONS]       [experimental] Watch for file changes and automatically trigger a deploy
  cdktf output [stack] [OPTIONS]      Prints the output of a stack
  cdktf debug                         Get debug information about the current project and environment
  cdktf provider                      A set of subcommands that facilitates provider management                                                                                                                             [aliases: outputs]
  cdktf completion                    generate completion script
 
Options:
  --version                   Show version number                                                                                                                                                                  [boolean]
  --disable-plugin-cache-env  Dont set TF_PLUGIN_CACHE_DIR automatically. This is useful when the plugin cache is configured differently. Supported using the env CDKTF_DISABLE_PLUGIN_CACHE_ENV. [boolean] [default: false]
  --log-level                 Which log level should be written. Only supported via setting the env CDKTF_LOG_LEVEL                                                                                                 [string]
  -h, --help                  Show help                                                                                                                                                                            [boolean]
 
Options can be specified via environment variables with the "CDKTF_" prefix (e.g. "CDKTF_OUTPUT")