In this talk we will explore a thought invoking DevOps concept of using agile development tools for source code management to manage environment configuration changes to ensure consistent and repeatable updates to running environments. The DevOps community often call the environment configuration changes that are stored in a version management system as "Infrastructure as Code". Another controversional point that will be covered is the question: "Who developes Infrastructure as Code?". We will introduce the notion of a new role called an "Infrastructure Engineer" into the vocabulary of the attendees as the role that would produce "Infrastructure as Code".