We can't always execute a binary to get what we want. A configuration done dynamically is a very common situation; system paths can be dynamic, users and passwords can be auto-generated, network ports can be contextual, third-party credentials will be different in development and in production, slaves will join their masters, cluster members will find other nodes, and most other similar changing elements will need to adapt at runtime. The trick here is to combine environment variables with the use of a script as an entry point that will be executed no matter what, and behave according to the environment variables, optionally combined with a command from the Dockerfile.
Infrastructure as Code (IAC) Cookbook
By :
Infrastructure as Code (IAC) Cookbook
By:
Overview of this book
Para 1: Infrastructure as code is transforming the way we solve infrastructural challenges. This book will show you how to make managing servers in the cloud faster, easier and more effective than ever before. With over 90 practical recipes for success, make the very most out of IAC.
Table of Contents (18 chapters)
Infrastructure as Code (IAC) Cookbook
Credits
About the Authors
About the Reviewer
www.PacktPub.com
Customer Feedback
Preface
Free Chapter
Vagrant Development Environments
Provisioning IaaS with Terraform
Going Further with Terraform
Automating Complete Infrastructures with Terraform
Provisioning the Last Mile with Cloud-Init
Fundamentals of Managing Servers with Chef and Puppet
Testing and Writing Better Infrastructure Code with Chef and Puppet
Maintaining Systems Using Chef and Puppet
Working with Docker
Maintaining Docker Containers
Index
Customer Reviews