DevOps/Infrastructure as Code: Difference between revisions

From Wiki
(→‎Automate Everything: Add description)
(→‎Automate Everything: small correction)
Line 3: Line 3:
===Automate Everything===
===Automate Everything===


The following are ordered in descending order of the amount of toil required.
The following are ordered in increasing order of the amount of toil required.


1. Redesign or reconfigure things so the task isn't necessary at all. <br />
1. Redesign or reconfigure things so the task isn't necessary at all. <br />

Revision as of 13:23, 6 June 2020

Infrastructure as Code Paradigm

Automate Everything

The following are ordered in increasing order of the amount of toil required.

1. Redesign or reconfigure things so the task isn't necessary at all.
2. Implement automation that handles the task transparently, without anyone needing to pay attention.
3. Implement a self-service tool so that the task can be done quickly, by someone who doesn't need to know the details, preferably the user or person who needs it done.
4. Write documentation so that users can easily carry out the task on their own.


Free resource to learn the basics:
https://assets.thoughtworks.com/assets/infrastructure-as-code/Infrastructure_as_Code_ThoughtWorks_Preview_Edition.pdf


An excellent tutorial on the topic:
https://github.com/Artemmkin/infrastructure-as-code-tutorial


Yevgeniy Brikman, author of a book on Terraform and founder of Gruntwork, wrote a great summary of the book (which cannot be reproduced here because Goodreads apparently has exclusive rights over reviews. Never writing anything there again.)
https://www.goodreads.com/review/show/1808566933