Unlike resources there is no proper way to configure dependency for providers. When we started out with using Terraform’s providers, we immediately ran into a problem. For example, the providers that we would be working with for our infrastructure are Amazon Web Services and Docker.
Their main objective is to expose resources like AWS instances, security groups, docker containers, etc. This is a term used by all tools developed by Hasicorp that can be seen as the integration point of the software. The way Terraform manages to compose multiple tiers is via providers. All of this is done by a single command only: terraform apply. Whenever there are changes in this configuration, Terraform will implement the changes. With Terraform there is a common configuration platform, a shared language to deploy the entire infrastructure of a modern datacenter. But the coolest and most interesting part is probably the fact that it manages to compose multiple tiers like IaaS, PaaS and SaaS. Next to that it also supports version control. Terraform is an example of IaC that converts your infrastructure to human friendly config files that are JSON compatible. This does not necessarily incline automation of infrastructure but has to be viewed as something separate.
Docker remote api tls code#
The base idea is to manage and provision your infrastructure by code (configuration files, scripts, etc). Infrastructure as Code (IaC), or basically programmable infrastructure, is a concept that has been in development for quite a few years now. Our desire by using Terraform is to easily deploy our infrastucture and orchestrate our Docker environment. We researched what it was all about, what its main advantages are and how we could use it for setting up our own infrastructure. Last week we delved deeper into Terraform, one of the newest projects developed by Hashicorp.
0 kommentar(er)
