Commit a29319a9 authored by Seth Floyd's avatar Seth Floyd

cleanup

parent 5c3bf993
......@@ -40,7 +40,7 @@ You put `TF_VAR_` on the front of any variables that Terraform will need to pass
# FILES TO EDIT
* `backend-state.tf` - Pretty obvious if you look at it.
* `outputs.tf` - Replace all of the `VPC_PRITUNL` entries with the name of your VPC that you also put in `vpc-utility.tf` Should be an easy copy and replace.
* `outputs.tf` - Replace all of the `VPC_PRITUNL` entries with the name of your VPC that you also put in `vpc.tf` Should be an easy copy and replace.
* `variables.tf` - Main setting for REGION is found here.
* `vpc.tf` - Be sure to change the options with comments
* `gitlab-ci.yml` - Rename this file to `.gitlab-ci.yml`. I added a DESTROY option at the end of the pipeline. If you plan on using this in any sort of "production" environment where you dont want anyone to accidentally rip the VPC out from under your stuff...delete this section. Dont just comment it out, DELETE it.
......
......@@ -50,7 +50,7 @@ plan:
apply:
stage: apply
environment:
name: Utility Stack
name: Pritunl VPN Stack
script:
- terraform apply "$PLAN"
dependencies:
......@@ -64,7 +64,7 @@ apply:
destroyplan:
stage: destroyplan
environment:
name: Utility Stack
name: Pritunl VPN Stack
script:
- terraform init -backend=true -get=true -input=false
- terraform plan -destroy -out=$DESTROYPLAN
......@@ -79,7 +79,7 @@ destroyplan:
destroy:
stage: destroy
environment:
name: Utility Stack
name: Pritunl VPN Stack
script:
- terraform init -backend=true -get=true -input=false
- terraform apply "$DESTROYPLAN"
......
......@@ -6,7 +6,7 @@ output "vpc_id" {
value = module.VPC_PRITUNL.vpc_id
}
output "utility_vpc_cidr_block" {
output "vpc_cidr_block" {
description = "The CIDR block of the VPC"
value = module.VPC_PRITUNL.vpc_cidr_block
}
......
......@@ -2,7 +2,7 @@
variable "region" {
default = "us-east-1"
}
#The following can be found in 1Password under the Terrform user for the tb-utility account:
variable "AWS_ACCESS_KEY_ID" {}
variable "AWS_SECRET_ACCESS_KEY" {}
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment