From b013315218499f337442e10c7dcd4c03295bb474 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Daniel=20P=C3=B6tzinger?= Date: Thu, 6 Apr 2017 23:29:45 +0200 Subject: [PATCH] link added --- radar/2017-03-01/devops-practices.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/radar/2017-03-01/devops-practices.md b/radar/2017-03-01/devops-practices.md index 2336e98..fc44692 100644 --- a/radar/2017-03-01/devops-practices.md +++ b/radar/2017-03-01/devops-practices.md @@ -29,7 +29,7 @@ As always, we are establishing "community of interests" to improve and promote t Another important aspect and also enabler of DevOps practices is the increase of certain tool and methods - some of them are also represented in the Tech Radar. For example: Puppet Environments; Docker; Cloud Services, Terraform, Consul etc. -**DevSetup = Prod Setup, Infrastructure as a Code** +**DevSetup = Prod Setup, [Infrastructure as a Code](methods-and-patterns/infrastructure-as-code.html)** Keeping the development infrastructure setup close to production is also a commonly implemented practice and a direct result of the "Infrastructure as Code" method. Handling infrastructure and the required changes and innovations in ways similar to those used for applications is important; you can ready more about this here: Infrastructure as Code