working on the plane for Days 58 - 61- work in progress

Days/day61.md

@@ -20,9 +20,29 @@ Each of the above do have their pros and cons though.
 ### terraform workspaces 
 
 Pros 
-- 
+- Easy to get started 
+- Convenient terraform.workspace expression 
+- Minimises code duplication 
+
+Cons
+- Prone to human error (we were trying to eliminate this by using TF)
+- State stored within the same backend 
+- Codebase doesnt unambiguously show deployment configurations.
+
+### File Structure 
+
+Pros 
+- Isolation of backends 
+    - improved security 
+    - decreased potential for human error 
+- Codebase fully represents deployed state
 
 Cons 
+- Multiple terraform apply required to provision environments 
+- More code duplication, but can be minimised with modules. 
+
+
+
 
 ## Resources 
 I have listed a lot of resources down below and I think this topic has been covered so many times out there, If you have additional resources be sure to raise a PR with your resources and I will be happy to review and add them to the list. 

Days/day62.md

@@ -1,5 +1,9 @@
 ## 
 
+Terragrunt 
+
+Terraform Cloud 
+
 ## Resources 
 I have listed a lot of resources down below and I think this topic has been covered so many times out there, If you have additional resources be sure to raise a PR with your resources and I will be happy to review and add them to the list. 
 

README.md

@@ -97,7 +97,7 @@ This will not cover all things DevOps but it will cover the areas that I feel wi
 - [✔️] 🤖 58 > [HashiCorp Configuration Language (HCL)](Days/day58.md)
 - [✔️] 🤖 59 > [Create a VM with Terraform & Variables](Days/day59.md)
 - [✔️] 🤖 60 > [Docker Containers, Provisioners & Modules](Days/day60.md)
-- [✔️] 🤖 61 > [](Days/day61.md)
+- [✔️] 🤖 61 > [Kubernetes & Multiple Environments](Days/day61.md)
 - [🚧] 🤖 62 > [](Days/day62.md)
 
 ### Automate Configuration Management