In the DevNet Associate course a lot of attention goes to "Infrastructure as Code", implying that we should stop to change configurations manually. Immutability and Idempotency are key terms. This videos explains the importance of making infrastructure changes indirectly.
Key Takeaways
Make changes indirectly and automatically
Use small composable modules
Validate the infrastructure works as expected
test entire deployments and not only units
Source
Y. Brikman, 5 Lessons Learned From Writing Over 300,000 Lines of Infrastructure Code, 35:31, HashiCorp,
Published on Youtube, 27 nov. 2018
URL: https://www.youtube.com/watch?v=RTEgE2lcyk4
Comments