4 min read
While working with terraform we might find some configuration or syntax errors using terraform plan. While we won't break anything anyway, it take a lot of time to realize we have a syntax error due to a typo. This is specially true if we are working with a remote terraform state. To avoid wasting time we can use terraform validate
11/06/2021
Read more...7 min read
Docker has the ability to handle multi architecture containers: Using the same container image and tag we can deploy it on multiple architectures such as Intel and ARM. Since a docker container is composed of multiple layers it will just use one or another depending on the architecture we are running it. From the user perspective there's no difference on it's usage, but how do we build them?
10/06/2021
Read more...2 min read
There are certain terraform outputs that can contain sensitive data, for example: Rendered helm values can contain sensitive data that we need to give to helm to be able to install the pods on our kubernetes cluster. Starting terraform 0.15 we can tell terraform which input and output variables are sensitives so it can hide them away from it's output.
For example, to set an output variable as sensitive we just need to add the sensitive attribute and set it to true:
output "helm_pet2cattle_values" {
value = module.pet2cattle.values
sensitive = true
}
09/06/2021
Read more...3 min read
If we need to create multiple resources of the same kind based on a set of objects, we can use the for_each keyword for creating them.
08/06/2021
Read more...3 min read
One of the first things we might want to know about an Oracle database we have just connected is what version it is running. We can retrieve this information using an SQL query
07/06/2021
Read more...