Abstract
Recent years have seen the rise of disciplines like continuous integration, test driven development, build/deployment automation, and more. All of these had a purpose to automate as many parts as possible of the lifecycle of a software product. However, the main focus often is the software itself, and the infrastructure on which the software runs is still quite often a “work of art.”
To make error is human. To propagate error to all server in automatic way is #devops. —DevOps Borat 1
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
Rights and permissions
Copyright information
© 2012 Michael Hüttermann
About this chapter
Cite this chapter
Hüttermann, M. (2012). Infrastructure as Code. In: DevOps for Developers. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4302-4570-4_9
Download citation
DOI: https://doi.org/10.1007/978-1-4302-4570-4_9
Publisher Name: Apress, Berkeley, CA
Print ISBN: 978-1-4302-4569-8
Online ISBN: 978-1-4302-4570-4
eBook Packages: Professional and Applied ComputingProfessional and Applied Computing (R0)Apress Access Books