|
|
| (2 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| == Infrastructure as Code Paradigm ==
| | Notes on DevOps practices and tools. |
|
| |
|
| === Automate Everything ===
| | <splist |
| 1. Redesign or reconfigure things so the task isn't necessary at all. <br/>
| | sortby=title |
| 2. Implement automation that handles the task transparently, without anyone needing to pay attention. <br/>
| | liststyle=unordered |
| 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. <br/>
| | showpath=no |
| 4. Write documentation so that users can easily carry out the task on their own.
| | kidsonly=no |
| | | debug=0 /> |
| 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/>
| |
| https://www.goodreads.com/review/show/1808566933
| |
Latest revision as of 03:54, 6 September 2020
Notes on DevOps practices and tools.
