DevOps/Infrastructure as Code: Difference between revisions

From Wiki
(→‎Automate Everything: small correction)
(Reorganize page)
 
Line 1: Line 1:
==Infrastructure as Code Paradigm==
===Automate Everything===
===Automate Everything===


Line 10: Line 8:
4. Write documentation so that users can easily carry out the task on their own.
4. Write documentation so that users can easily carry out the task on their own.


=== Resources ===


 
* Free resource to learn the basics: <br />https://assets.thoughtworks.com/assets/infrastructure-as-code/Infrastructure_as_Code_ThoughtWorks_Preview_Edition.pdf
Free resource to learn the basics: <br />https://assets.thoughtworks.com/assets/infrastructure-as-code/Infrastructure_as_Code_ThoughtWorks_Preview_Edition.pdf
* An excellent tutorial on the topic: <br />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.) <br />
 
An excellent tutorial on the topic: <br />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.)<br />
https://www.goodreads.com/review/show/1808566933
https://www.goodreads.com/review/show/1808566933

Latest revision as of 13:32, 6 June 2020

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.

Resources

https://www.goodreads.com/review/show/1808566933