Show Plan
```
terraform
aws_lightsail_static_ip.vita_db_ip: Refreshing state... [id=vita_db_ip]
aws_lightsail_key_pair.vita_db_key: Refreshing state... [id=vita_db_key]
local_sensitive_file.private_key: Refreshing state... [id=a12e017de5591d47aabe7df620e2ac133d4ff801]
aws_lightsail_instance.vita_db: Refreshing state... [id=mongo-enterprise]
aws_lightsail_static_ip_attachment.vita_db_ip_attach: Refreshing state... [id=vita_db_ip]
local_file.ansible_inventory: Refreshing state... [id=202deff6be481ce2628572c84d5dd563955411c0]
aws_lightsail_instance_public_ports.vita_db_ports: Refreshing state... [id=mongo-enterprise-219416181]
Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
+ create
Terraform will perform the following actions:
# local_file.ansible_inventory will be created
+ resource "local_file" "ansible_inventory" {
+ content = <<-EOT
[mongo-enterprise]
13.215.187.166
[mongo-enterprise:vars]
ansible_ssh_common_args='-o StrictHostKeyChecking=accept-new'
EOT
+ directory_permission = "0777"
+ file_permission = "0777"
+ filename = "./provisioning/inventory"
+ id = (known after apply)
}
# local_sensitive_file.private_key will be created
+ resource "local_sensitive_file" "private_key" {
+ content = (sensitive value)
+ directory_permission = "0700"
+ file_permission = "0400"
+ filename = "./private.key"
+ id = (known after apply)
}
Plan: 2 to add, 0 to change, 0 to destroy.
─────────────────────────────────────────────────────────────────────────────
Note: You didn't use the -out option to save this plan, so Terraform can't
guarantee to take exactly these actions if you run "terraform apply" now.
```
Terraform Format and Style 🖌
successTerraform Initialization ⚙️
successTerraform Validation 🤖
successTerraform Plan 📖
successShow Plan
``` terraform aws_lightsail_static_ip.vita_db_ip: Refreshing state... [id=vita_db_ip] aws_lightsail_key_pair.vita_db_key: Refreshing state... [id=vita_db_key] local_sensitive_file.private_key: Refreshing state... [id=a12e017de5591d47aabe7df620e2ac133d4ff801] aws_lightsail_instance.vita_db: Refreshing state... [id=mongo-enterprise] aws_lightsail_static_ip_attachment.vita_db_ip_attach: Refreshing state... [id=vita_db_ip] local_file.ansible_inventory: Refreshing state... [id=202deff6be481ce2628572c84d5dd563955411c0] aws_lightsail_instance_public_ports.vita_db_ports: Refreshing state... [id=mongo-enterprise-219416181] Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols: + create Terraform will perform the following actions: # local_file.ansible_inventory will be created + resource "local_file" "ansible_inventory" { + content = <<-EOT [mongo-enterprise] 13.215.187.166 [mongo-enterprise:vars] ansible_ssh_common_args='-o StrictHostKeyChecking=accept-new' EOT + directory_permission = "0777" + file_permission = "0777" + filename = "./provisioning/inventory" + id = (known after apply) } # local_sensitive_file.private_key will be created + resource "local_sensitive_file" "private_key" { + content = (sensitive value) + directory_permission = "0700" + file_permission = "0400" + filename = "./private.key" + id = (known after apply) } Plan: 2 to add, 0 to change, 0 to destroy. ───────────────────────────────────────────────────────────────────────────── Note: You didn't use the -out option to save this plan, so Terraform can't guarantee to take exactly these actions if you run "terraform apply" now. ```Pusher: @Mike2060, Action:
pull_request