Kubernetes provider for terraform: kubernetes_manifest

2 min read

Since version 2.8.0 of the Kubernetes provider for terraform, the kubernetes_manifest resource is no longer considered experimental. With this resource we can push any kind of Kubernetes objects using terrraform that doesn't have a specific resource for it:

resource "kubernetes_manifest" "example_km" { manifest = yamldecode(<<-EOF apiVersion: v1 kind: Namespace metadata: name: example-ns annotations: test: example EOF ) } 

11/02/2022

Terraform: aws_security_groups empty list of SecurityGroups

2 min read

Update 10/02/2020: The new version 4.0 of the AWS provider have been released. At this point, all AWS provider plural data sources (like the aws_security_groups) that return an array of results will now return an empty list if zero results are found.

Prior to that, if when trying to use the aws_security_groups data source if the tags did not match any SecurityGroup, terraform would have returned an error instead of an empty list:

data "aws_security_groups" "eks-pod" { tags = { "NotAnActualTag" = "WontMatchAnything" } } 

21/10/2021

How to override a provider with a local version

2 min read

If we are modifying a provider, to be able to properly test it we might want to run a terraform plan or apply using this provider. To be able to override a given provider using this method (dev_overrides) we will need to use terraform v0.14 or later

14/10/2021

terraform: AWS provider - missing region

1 min read

We might face the following error when trying to apply terraform:

$ terraform plan Acquiring state lock. This may take a few moments... Error: Missing required argument The argument "region" is required, but was not set. Releasing state lock. This may take a few moments... 

16/02/2021