@sumanthraman Freshers get in lakhs from 0. Technically you can’t decide based on past of the candidate. But you can share your budget and scope of the work.
🚀 Terraform Tip #12 (SRE) Pin provider versions & use required_providers block to prevent silent drift in prod. Stability > latest.
How do you lock your providers? 👇
#SRE#Terraform#IaC#Datadog#Dynatrace#PulseTechOps
🚀 Terraform Tip #12 (SRE) Pin provider versions & use required_providers block to avoid surprise breaking changes in prod. Stability > latest.
Which provider surprises have you fought? 👇
#SRE#Terraform#IaC#Datadog#Dynatrace#PulseTechOps
🚀 Terraform Tip #13 (SRE) Pin provider versions with required_providers block + constraint operators (>=, ~>). Avoid surprise breaking changes in prod.
Which version pinning strategy do you prefer? 👇
#SRE#Terraform#IaC#Datadog#Dynatrace#PulseTechOps
🚀 Terraform Tip #12 (SRE) Use terraform_data + external data source to fetch Datadog monitor IDs dynamically and enforce drift detection. Zero manual updates!
How do you currently handle cross-tool references? 👇
#SRE#Terraform#IaC#Datadog#Dynatrace#PulseTechOps
🛠️ Terraform Tip #11 (SRE)
Use `terraform workspace` for env isolation (dev/staging/prod).
Separate state files → safe parallel changes to observability configs.
No cross-env pollution.
Your workspace tip? 👇
#SRE#Terraform#IaC#Datadog#Dynatrace#PulseTechOps
🛠️ Terraform Tip #10 (SRE)
Use `null_resource` + `local-exec` for Datadog/Dynatrace post-apply hooks.
Trigger API calls or scripts after resource creation.
Great for non-TF integrations.
Your hook pattern? 👇
#SRE#Terraform#IaC#Datadog#Dynatrace#PulseTechOps