revise infrastructure section on README

README.md

@@ -89,41 +89,21 @@ We have created the infrastructure by using Terraform. The infrastructure consis
 	- Option 2: Set environment variable
 		- `export AWS_ACCESS_KEY_ID=<KEY>`
 		- `export AWS_SECRET_ACCESS_KEY=<SECRET>`
-- Create `ESK Cluster`
-	- `cd infra/iac/eks`
+- Provision the infrastructure (ESK, RDS (Postgres), SonarQube, ArgoCD, Cloudflare, VPC)
+	- `cd infra/iac`
 	- `terraform init`
 	- `terraform apply`
-	- `Terraform` will require `Cloudflare` API key, you can get it from the `Cloudflare` dashboard
-		- Option 1: Enter API token on Terraform prompt
-		- Option 2: Export environment variable that provide for Terraform
-	- And then Terraform will proceed to create the EKS Cluster
+	- `Terraform` will require
+      - `cloudflare` API key, you can get it from the `Cloudflare` dashboard
+          - Option 1: Enter API token on Terraform prompt
+          - Option 2: Export environment variable that provide for Terraform
+      - `RDS` username, password, and database name
+		  - Option 1: Enter the value on Terraform prompt
+		  - Option 2: Export environment variable that provide for Terraform
+	- And then Terraform will do things for you
 	- Waiting and enjoy your coffee
-- Create `RDS (Postgres)`
-	- `cd infra/iac/rds`
-	- `terraform init`
-	- `terraform apply -auto-approve`
-	- You need to input username and password for the RDS
-	- Terraform will create the RDS
-	- And then output the RDS endpoint
-- Create `SonarQube`
-	- `cd infra/iac/sonarqube`
-	- `terraform init`
-	- `terraform apply -auto-approve`
-	- You need to input `Cloudflare` API key
-	- Terraform will create the `SonarQube`
-	- And then output the SonarQube endpoint
-	- You can access default username and password via `infra/iac/sonar/ansible`
-	- Run `make get-cred` in Ansible directory
-- Mapping DNS with `Cloudflare`
-	- We have created the DNS mapping for every group in the workshop such as:
-	- Dev
-		- `group-1-b2-dev`: `group-1-b2-dev.werockstar.dev`
-	- Prod
-		- `group-1-b2-prod`: `group-1-b2-prod.werockstar.dev`
-- Create `ArgoCD` application (No need to do anything because we have done it for demo purpose)
-	- ArgoCD will automatically deploy the application to the EKS cluster
-- Importantly, you need to destroy the infrastructure after the workshop
-	- `terraform destroy` in each directory
+- Importantly, you need to destroy resources because it's not free 💰
+	- `terraform destroy`
 
 ### Step 1: Fork the repository and setup Github Actions ✅
 - Fork `workshop-summer` repository and name it as `workshop-summer-<GROUP_NO>-<BATCH_NO>` (e.g. `workshop-summer-group-1-b2`)