ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
DevOps & observability · #pulumi
Learn the requirements, minimal design, trust boundaries, operational checks, failure modes, and change triggers for Pulumi Stack References to safely share data between stacks.
Learn how to expose a value from one Pulumi stack and consume it in another using Stack References, with step‑by‑step commands, verification steps, and rollback guidance.
Stop duplicating infrastructure code for dev and prod. Learn how to use Pulumi Stacks to isolate environments, manage per-stack configurations, and secure secrets.
Learn how to diagnose and resolve Pulumi state lock conflicts in shared backends to prevent state corruption and restore your deployment pipeline.
Goal: Determine whether Pulumi can automatically detect and renew an expired Azure AD service‑principal secret when using static credentials, while maintaining least‑privilege access. Constraints/uncertainty: Pulumi reads the secret from environment or config per command; static secrets are not auto‑refreshed, whereas Managed Identity or OIDC flows rely on t