ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Wrap an S3 bucket and CloudFront distribution into a Pulumi component resource so you can deploy static blogs repeatedly without copying infrastructure code.
Use Terramate stack dependencies and terramate run to execute Terraform commands across multiple stacks in the correct order.
Run terraform plan and apply only in stacks with modified files using terramate run --only-changed, reducing execution time and preventing unintended infrastructure changes.
Terramate adds a stack-and-blueprint orchestration layer above Terraform to eliminate copy-paste drift across accounts and regions. This post walks through a concrete VPC blueprint, generated HCL, and the run-time orchestration that keeps large fleets consistent.
Use a single ESC environment per stage, keep secrets out of Pulumi state, and validate ESC schema and access logs to ensure deterministic, auditable deployments.
Stop relying on manual UI edits for your Grafana dashboards. Learn how to use file-based provisioning to implement a version-controlled, code-first monitoring workflow.
Learn how to use Packer shell provisioners with external scripts to automate software installation during image builds, avoid drift, and ensure privilege escalation.
Terraform's for_each meta-argument solves count's index-shift problem by addressing resources with stable keys. See a worked IAM example, targeting commands, and the plan-time trade-offs to watch.
Move Bamboo build plans out of the UI and into versioned YAML specs so changes go through pull requests instead of untracked clicks.
pulumi
terraform
grafana
prometheus
bamboo