ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Pulumi stacks are isolated instances of your infrastructure program, not code copies. Learn how to use config files and Stack References to manage dev, staging, and prod without forking your code.
A decision guide for passing infrastructure outputs between Pulumi stacks, comparing Stack References with config, external secrets, and GitOps, plus a TypeScript implementation pattern.
Engineering teams often struggle to maintain consistent access control and extensibility across Docker and Kubernetes clusters managed by Portainer. This blog outlines a practical RBAC scoping plugin and version-alignment strategy.
Make Terraform deploy graphs explicit with Terramate stacks, render shared backend and provider config via code generation, and run only changed stacks to cut CI time and blast radius.
Application Sets let you generate multiple Argo CD Apps from one template and value list. This post covers configuration, a working example, and version-aware checks.
Hardcoded environment values cause drift; Pulumi stack references propagate outputs cleanly across dev, staging, and prod stacks, with verification steps to keep them reliable.
Learn how to use a single Argo CD ApplicationSet to manage multiple environments securely, with clear trust boundaries, operational checks, and failure‑mode awareness.
pulumi
terraform
argocd