Skip to content

Commit e5f27ae

Browse files
authored
Update README.md
1 parent a043b56 commit e5f27ae

File tree

1 file changed

+15
-6
lines changed

1 file changed

+15
-6
lines changed

README.md

Lines changed: 15 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -80,18 +80,27 @@ This workflow requires the following secrets to be configured in your GitHub rep
8080
* resource_owner = "Your-name"
8181
* aws_region = "AWS Region" ex. us-east-1
8282
* azs = ["us-east-1a", "us-east1b"] - Change to Correct Availability Zones based on selected Region
83-
* Also update assets boolean value as per your work-flows
8483

85-
**STEP 3:** In the `S3 directory`, inside the `variable.tf` file modify the following data
86-
* description = "S3 bucket for Terraform remote state storage"
84+
85+
**STEP 3:** Modify the `S3/variable.tf` file inside the `S3 directory`.
8786
* default = "your-unique-bucket-name" # Replace with your actual bucket name
88-
8987

90-
**STEP 4:** Commit and push your build branch to your forked repo
88+
**STEP 4:** Modify the `Backend.tf` file in the `Infra/Backend.tf`, `eks-cluster/Backend.tf`, `Nap/Backend.tf`, `Policy/Backend.tf`, `Arcadia/Backend.tf` directory.
89+
*bucket = "your-unique-bucket-name" # Your S3 bucket name
90+
* key = "infra/terraform.tfstate" # Path to state file
91+
* region = "your-aws-region-name" By default us-east-1
92+
93+
**STEP 5:** Add the name of your S3 bucket inside the `NGINX V5-NIC/NAP Destroy` workflow file.
94+
*name: Set Bucket Name
95+
* id: set_bucket
96+
* run: |
97+
* echo "bucket_name="your-unique-bucket-name" >> $GITHUB_OUTPUT
98+
99+
**STEP 6:** Commit and push your build branch to your forked repo
91100
* Build will run and can be monitored in the GitHub Actions tab and TF Cloud console
92101

93102

94-
**STEP 5:** Once the pipeline is complete, verify that your assets were deployed or destroyed based on your workflow.
103+
**STEP 7:** Once the pipeline is complete, verify that your assets were deployed or destroyed based on your workflow.
95104

96105
**NOTE:** The autocert process takes time. It may be 5 to 10 minutes before Let's Encrypt has provided the cert.
97106

0 commit comments

Comments
 (0)