ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
DevOps & observability · #terraform
A performance change should improve the measured workload without sacrificing correctness or wasting capacity. Which measurements and bottlenecks should be considered first?
I'm getting confused when using Terraform to provision an auto-scaling group. Should I use launch configuration or launch template for EC2 properties, such as which AMI, instance types, ...? I don't know what the difference is between them, which we should use and why they exist?
Every Terraform guide on the web provides a partial solution that is almost always not the real picture. I get that not everyone has the same infrastructure needs, but what worries me is that the common scenario, including: Multiple environments (e.g. dev , stage ) Remote backend (e.g. AWS S3) Some basic resources (e.g. S3 buckets or EC2 instances) isn't pre
Just today, whenever I run terraform apply , I see an error something like this: Can't configure a value for "lifecycle_rule": its value will be decided automatically based on the result of applying this configuration. It was working yesterday. Following is the command I run: terraform init && terraform apply Following is the list of initialized prov
An upgrade needs a compatibility check, a tested release and a recovery path. Which changes deserve particular attention before the new version reaches production?
I'm trying to do the azure service principle password rotation using Terraform, with the latest versions of azuread they have provided this rotation feature, resource "time_rotating" "test" { rotation_years = 5 lifecycle { create_before_destroy = true } } resource "azuread_service_principal_password" "service_principal_password" { service_principal_id = var.
I have some Terraform code with an aws_instance and a null_resource : resource "aws_instance" "example" { ami = data.aws_ami.server.id instance_type = "t2.medium" key_name = aws_key_pair.deployer.key_name tags = { name = "example" } vpc_security_group_ids = [aws_security_group.main.id] } resource "null_resource" "example" { provisioner "local-exec" { command
Compare suitability, operational responsibilities and limits before choosing this technology for a project. Which trade-offs should guide the decision?
Is there a way to conditionally add statement blocks in aws_iam_policy_document ? I'm looking for something like: data "aws_iam_policy_document" "policy" { statement { sid = "PolicyAlways" ... } if (var.enable_optional_policy) { statement { sid = "PolicySometimes" ... } } }
azure
ansible