Closed fmunteanu closed 4 years ago
Hi @fmunteanu
Would you mind including an example of use in the example folder?
Thanks!
Good morning @edbizarro, let me know if is satisfactory. This is an example, while planning:
# module.airflow_cluster.module.sg_airflow.aws_security_group.this_name_prefix[0] will be created
+ resource "aws_security_group" "this_name_prefix" {
+ arn = (known after apply)
+ description = "Security group for floren-dev-airflow machines"
+ egress = (known after apply)
+ id = (known after apply)
+ ingress = (known after apply)
+ name = (known after apply)
+ name_prefix = "floren-dev-airflow-sg-"
+ owner_id = (known after apply)
+ revoke_rules_on_delete = false
+ tags = {
+ "Name" = "floren-dev-airflow-sg"
+ "Namespace" = "floren"
+ "Role" = "airflow-infrastructure"
+ "Stage" = "dev"
+ "Team" = "AI Labs"
}
+ vpc_id = "vpc-08269f58d24108b45"
}
At Expedia we tag resources with specific tags related to project, etc. If these tags are not present, resources will be automatically deleted. Therefore, I implemented the missing tags into
terraform-terraform-label
modules.I also added a specific version for the
terraform-terraform-label
source. With the cluster in production, usingmaster
will definitely introduce a risk factor, as mentioned into their documentation. Unfortunately, we cannot use variables into source.From their documentation: