blog: add "Bring Your Terraform Estate Into the Agentic Era" launch post by djperlovsky · Pull Request #20569 · pulumi/docs

djperlovsky · 2026-07-29T21:03:00Z

Proposed changes

Adds the Win Workloads from Terraform launch blog post, staged for publication on 2026-08-04 at 9:00 AM Pacific (date: 2026-08-04T09:00:00-07:00). The post won't appear on the live site until a deploy runs on or after that timestamp, so this is safe to merge ahead of the date.

The post announces:

GA of Pulumi Cloud as a backend for Terraform state (remote plans/applies, manual approvals, RBAC, Neo code reviews, preventive policies, ESC-hosted config)
GA of HCL as a first-class language in Pulumi IaC, 100% OpenTofu compatible
Native Terraform module support in Pulumi programs, plus Terraform modules in the Pulumi Cloud private registry
The continued HashiCorp transition offers (credit escape hatch, free modernization workshop, ROI calculation)

It follows on from Joe Duffy's December post, Pulumi for All Your IaC — Including Terraform and HCL, and links back to it as the setup rather than restating it.

Frontmatter: author daniel-perlovsky, category product, tags infrastructure-as-code / terraform / hcl / pulumi-cloud (all from the canonical vocabulary).

Related PRs

Docs for the capabilities announced here ship in #20570 (remote execution, preventative policy enforcement on Terraform plans, manual approval for VCS-triggered applies). Review the two together — verifying this post against master alone will flag the remote-execution and preventive-policy claims as unsupported, because those docs are not on master yet.

Notes for reviewers

feature.png — rendered at 1884x1256 from the rocket (launch/announcement) template
Social copy for X / LinkedIn / Bluesky — drafted and applied per the social-review check
The "over 40% of our users now manage infrastructure using AI agents" stat — confirmed current by the author for the Aug 4 publish date

All internal doc links were verified to resolve against current paths: /docs/iac/get-started/terraform/terraform-state-backend/, /docs/iac/get-started/terraform/convert-hcl/, /docs/iac/get-started/terraform/terraform-modules/, /docs/administration/access-identity/rbac/, /docs/ai/neo/code-reviews/, /docs/insights/policy/, /docs/esc/, /docs/install/.

make lint passes locally on the post (0 errors).

🤖 Generated with Claude Code

Closes https://github.com/pulumi/marketing/issues/1781.

Staged for publication on 2026-08-04 at 9:00 AM Pacific. Announces the GA of Pulumi Cloud as a Terraform state backend, HCL as a first-class Pulumi IaC language, and native Terraform module support, along with the continued HashiCorp transition offers. Follows on from Joe Duffy's December post, "Pulumi for All Your IaC — Including Terraform and HCL," and links back to it as the setup. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

The shared placeholder copied by /new-blog-post is 942x628, which fails the markdown linter's feature-image dimension check. Replace it with a rocket template render (the launch/announcement template) at the required 1884x1256. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

github-actions · 2026-07-29T21:16:43Z

Social Media Review

content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md

X — PASS

LinkedIn — PASS

Bluesky — PASS

Suggestions (advisory)

These are stylistic notes — they don't block the post.

X

Opening sentence names all three shipped features outright, leaving nothing for the article to reveal
Opens with "Pulumi Cloud" instead of the sharper "rip out Terraform" hook in sentence two
"Here's what shipped" is a flat pointer given the feature list already stated

LinkedIn

Second paragraph names every feature (remote plans/applies, RBAC, Neo code reviews, HCL, module import) — the article has nothing new to add
"Today that vision ships" + "Here's the full breakdown of what shipped today" reads as a launch announcement, not a teaser

Bluesky

Lists all three shipped items outright, closing the gap the article would otherwise fill
"Move into the agentic infrastructure era" is a vague trend phrase, not a concrete detail
"Here's what shipped today" is redundant once the opener already states what shipped

Updated for commit 48159c0418cd839287f59aff122286df185bcfeb (short: 48159c0) at 2026-07-31 21:51 UTC.

Fills the blank twitter/linkedin/bluesky frontmatter fields with the copy drafted by the social-review check. All three tee up the post without delivering the announcement, and deliberately omit the "over 40% of users" stat pending a freshness check before the Aug 4 publish date. X 235/255, LinkedIn 692/2950, Bluesky 259/300. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

djperlovsky · 2026-07-29T21:18:20Z

Applied the suggested copy verbatim for all three platforms in ee624b8d54 — X 235/255, LinkedIn 692/2950, Bluesky 259/300. Agreed on leaving the "over 40% of users" stat out of the social copy until that number is confirmed fresh for the Aug 4 date.

On the social card note: the image is unreachable because it's generated at build time from the title + feature.png, and this post hasn't been deployed yet — it should resolve once the branch builds with the 1884x1256 feature image that landed in c48fc45148.

🤖 Addressed by Claude Code

pulumi-bot · 2026-07-29T21:28:59Z

Your site preview for commit 1ce6db8 is ready! 🎉

http://www-testing-pulumi-docs-origin-pr-20569-1ce6db81.s3-website.us-west-2.amazonaws.com

Changed pages:

/blog/bring-your-terraform-estate-into-the-agentic-era/

cnunciato

Nice work! A few minor suggestions, and I might come back and add a few links, but this is solid. Well done.

cnunciato · 2026-07-30T23:38:20Z

+
+The agentic infrastructure era is already here, and we want you to bring your IaC to it. [Get started with Pulumi free](/docs/install/) and provision your first stack in minutes.
+
+If you'd like to get started with the new Terraform/OpenTofu and HCL capabilities, or take advantage of the financial flexibility options, please [get in touch](/contact/?form=sales).


There are also other ways for practitioners to get started (templates, etc.), but we can also hold off and link from here to my post when it's ready.

No change made — whether to link out to your forthcoming getting-started post is the author's call (and depends on your post's timing vs. the Aug 4 publish date). Flagged for @djperlovsky.

🤖 Addressed by Claude Code

Copy edits for parallelism and clarity in the Terraform backend bullets, plus: - Reframe the interop claim as "Pulumi is now fully interoperable with Terraform and OpenTofu" - Note that remote-by-default plans/applies follow HCP Terraform and Terraform Enterprise behavior - Point the HCL link at the HCL language docs rather than the convert guide - Add a "learn more" docs link at the end of each of the three capability sections - Link "Get started with Pulumi free" to app.pulumi.com/signup Two review questions are left for the author: whether to move the modules section ahead of HCL, and whether to link out to Christian's forthcoming getting-started post. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Per review feedback, the three capability sections now follow an adoption progression: bring state to Pulumi Cloud, reuse the modules you already have, then write HCL natively. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

github-actions · 2026-07-31T21:25:19Z

Pre-merge Review — Last updated 2026-07-31T21:19:35Z

Tip

Summary: This is a new launch post announcing three Terraform-interop milestones (Pulumi Cloud as a GA Terraform state backend, HCL GA as a first-class Pulumi language, native Terraform module import), paralleling the December post it cites, all-iac-including-terraform-and-hcl. The wrongness that would hurt a reader here is capability overreach: several sentences promise more than the shipping feature's own docs describe (preventive policies on Terraform-backed stacks, "all of the capabilities," remote execution), plus two customer-facing numbers — "over 40% of our users" and Snowflake's "weeks to hours" — that don't match Pulumi's published figures. Two of those overreaches also ride the social.* frontmatter, which auto-posts on merge. Passes run: external claim verification over 57 extracted claims, a cited-link spot-check, a frontmatter sweep (body + meta_desc + all three social fields), a temporal-recency sweep, a readthrough coherence pass, and prose linting. Hugo preflight was skipped (content-only change) and no code blocks were present, so neither build nor code-example checks contributed.

Review confidence:

Dimension	Level	Notes
mechanics	MEDIUM	Frontmatter parses and all link targets resolve, but the Hugo preflight was skipped for this content-only PR — the real build runs in `build-and-deploy.yml`.
facts	MEDIUM	6 claims came back contradicted and 3 unverifiable; two verdicts on the remote-plans feature disagree with each other (see L27), so the remote-execution question needs an author answer rather than a reviewer ruling.
coherence	HIGH

Investigation log

Cross-sibling reads: not run (not in a templated section)
External claim verification: 42 of 57 claims verified (3 unverifiable, 6 contradicted) · 4 specialists (numerical, cross-reference, capability, framing); 0 cross-specialist corroborations · routed: 0 inline, 41 Pass 1, 1 Pass 2 (verified 1, contradicted 0, unverifiable 0), 15 Pass 3 (verified 10, contradicted 3, unverifiable 2).
Cited-claim spot-checks: 1 of 1 cited claims fetched and compared
Frontmatter sweep: ran on body + meta_desc + social.{bluesky, linkedin, twitter}
Temporal-trigger sweep: ran (recency words present in diff; spot-check in-review)
Code execution: not run (no static/programs/ change)
Code-examples checks: not run (no fenced code blocks in content files)
Editorial-balance pass: ran (single-subject, N/A)

🚨 Outstanding	⚠️ Low-confidence	💡 Pre-existing	✅ Resolved
5	10	0	0

🔍 Verification trail

57 claims extracted · 42 verified · 3 unverifiable · 6 contradicted

L3 in content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md "date: 2026-08-04T09:00:00-07:00" → ➖ not-a-claim (evidence: This is a frontmatter date field setting the scheduled publish time for a blog post, not a falsifiable factual assertion that can be verified against an external source.; source: content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md L3)
L5 in content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md "Pulumi supports native Terraform module support, in addition to Pulumi Cloud as a Terraform backend and HCL in Pulumi IaC being GA." → ✅ verified (evidence: The blog post itself and sibling Pulumi blog posts confirm all three elements: "Similar to Terraform support in Pulumi Cloud, HCL is now generally available as a first-class Pulumi language" (all-iac-including-terraform-and-hcl), "This fea…; source: repo:content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md; gh search code --owner pulumi "terraform module support")
L21 in content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md "Pulumi Cloud is now generally available (GA) as a backend for Terraform state." → ✅ verified (evidence: The blog body states: "We are excited to announce the general availability of [Pulumi Cloud as the backend to your Terraform state]," and the linked docs page at content/docs/iac/get-started/terraform/terraform-state-backend.md describes t…; source: repo:content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md; repo:content/docs/iac/get-started/terraform/terraform-state-backend.md)
L21 in content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md "Neo code reviews use what Pulumi Cloud knows about a user's running infrastructure to give feedback, on every pull request, on whether it's safe to merge chang…" (also L27, L33, L44-46, L48, L52-53, L57-60, L66, L74) → ✅ verified (evidence: The blog text itself matches: "Take advantage of Neo code reviews. On every pull request, leverage what Pulumi Cloud knows about your running infrastructure and get clear feedback on whether it's safe to merge changes to your Terraform and…; source: repo:content/docs/ai/neo/code-reviews/_index.md and repo:content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md)
L23 in content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md "You don't have to rip out Terraform to build for the agentic era. Here's what shipped." → ➖ not-a-claim (evidence: This is an introductory/marketing sentence summarizing the blog post's own content ("Here's what shipped"), not a falsifiable technical assertion about a product or third party.; source: repo:content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md)
L25 in content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md "Last December, Pulumi CEO Joe Duffy laid out Pulumi's vision to support all of an organization's infrastructure as code, including Terraform and HCL." (also L44) → ✅ verified (evidence: The referenced Pulumi blog post "Pulumi for All Your IaC — Including Terraform and HCL" was published Dec 18, 2025, and quotes Joe Duffy laying out plans for Pulumi Cloud to support Terraform/OpenTofu and for Pulumi's IaC tool to support H…; source: https://www.pulumi.com/blog/all-iac-including-terraform-and-hcl/)
L25 in content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md "Joe Duffy laid out Pulumi's vision to support all of your infrastructure as code, including Terraform and HCL, last December." → ✅ verified (evidence: Joe Duffy authored the Pulumi blog post "Pulumi for All Your IaC — Including Terraform and HCL," published Dec 18, 2025, announcing "three new ways Pulumi is enabling customers of HashiCorp, an IBM Company, who want a better, open source f…; source: https://www.pulumi.com/blog/all-iac-including-terraform-and-hcl/)
L25 in content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md "At Pulumi, we are building the platform for agentic infrastructure. Pulumi Cloud provides the guardrails and enterprise readiness needed to safely move fast in…" → ❌ contradicted (framing: shifted — source metric is "20% of infrastructure deployments" (a deployment-volume metric with projected growth to 50%) vs. claim's "40% of users manage infra…; evidence: (escalated from pass1) Pulumi's own publicly stated figures (CEO Joe Duffy, multiple 2026 blog/release posts) consistently cite "LLMs are now doing over 20% of infrastructure deployments, up from virtually zero a year ago," projected to gr…; source: https://www.pulumi.com/releases/agentic-infrastructure-era/; intuition: Claim's "40% of users" figure doesn't match any number found in Pulumi's own public statements, which consistently use…)
L27 in content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md "Remote plans and applies work against existing Terraform stacks via Pulumi Cloud." → ❌ contradicted (framing: shifted — blog claims "remote plans and applies... execute on a Pulumi-hosted runner"; the sibling docs page for the same feature says operations continue via…; evidence: The blog claims "Plans and applies run remotely by default... it executes on a Pulumi-hosted runner rather than your local machine," but the linked implementing docs page (content/docs/iac/get-started/terraform/terraform-state-backend.md)…; source: repo:content/docs/iac/get-started/terraform/terraform-state-backend.md; intuition: Blog's "remote runner" framing for a feature documented elsewhere as purely a state backend (local CLI execution) is su…)
L29 in content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md "Pulumi offers a credit escape hatch allowing customers to apply credits purchased from HashiCorp toward Pulumi usage until their next contract renewal." (also L84-86) → ❌ contradicted (evidence: The blog post itself states: "An escape hatch for your current contract... we're letting you apply credits purchased from HashiCorp toward your Pulumi usage until your next renewal, avoiding double pay." This is Pulumi's own first-party pr…; source: repo:content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md (L84))
L31 in content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md "Here's the full breakdown of what shipped today." → ➖ not-a-claim (evidence: This is an editorial transition sentence introducing the blog's own list of announced features, not a falsifiable third-party assertion.; source: repo:content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md)
L31 in content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md "Last December, our CEO Joe Duffy laid out his vision to make Pulumi the platform for all of your infrastructure a…" → ✅ verified (evidence: The linked post content/blog/all-iac-including-terraform-and-hcl/index.md is authored by joe-duffy, dated 2025-12-18 ("Last December" relative to this newer post), titled "Pulumi for All Your IaC — Including Terraform and HCL," and states…; source: repo:content/blog/all-iac-including-terraform-and-hcl/index.md)
L33 in content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md "Terraform modules import into Pulumi without changes." → ✅ verified (evidence: Pulumi's Terraform Module feature lets users consume Terraform modules directly. Official docs state: "Pulumi allows you to use existing Terraform modules directly in your Pulumi programs without converting or rewriting them" and "This all…; source: https://www.pulumi.com/docs/iac/adopting-pulumi/migrating-to-pulumi/from-terraform/ and https://www.pulumi.com/docs/iac/get-started/terraform/terraform-modules/)
L35 in content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md "Here's what shipped today." → ➖ not-a-claim (evidence: "Here's what shipped today" is a promotional framing statement referring to the blog post's own publication date, not a falsifiable third-party assertion.; source: repo:content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md)
L35 in content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md "We are excited to announce the general availability of [Pulumi Cloud as the backend to your Terraform state](/docs/iac/get-started/terraform/terraform-state-ba…" → ✅ verified (evidence: The linked page content/docs/iac/get-started/terraform/terraform-state-backend.md exists on pulumi/docs master, and companion blog content confirms: "Pulumi Cloud can serve as a Terraform state backend, letting you store and manage Terrafo…; source: gh api repos/pulumi/docs/contents/content/docs/iac/get-started/terraform (terraform-state-backend.md); gh search code --owner pulumi terraform-state-backend)
L37 in content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md "We recognize there is lots of infrastructure that works as is, and switching over to a new management paradigm is just not worth the squeeze. Pulumi Cloud supp…" → ✅ verified (evidence: The blog post itself and multiple sibling docs consistently describe this exact feature: "Pulumi Cloud can store Terraform state for teams that want encrypted state, update history, state locking, RBAC, and audit policies while continuing…; source: repo:content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md (L46-50); repo:content/docs/iac/comparisons/terraform/_index.md)
L38 in content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md "Pulumi is launching three ways to let customers avoid trading off building for the future against building for today, as of this post's publication." → ✅ verified (evidence: Line 38 of the source file states verbatim: "Today, we are launching three ways that Pulumi lets you avoid trading off building for the future against building for today." This is an exact paraphrase of the claim.; source: repo:content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md)
L38 in content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md "Over 40% of Pulumi's users now manage infrastructure using AI agents." → ❌ contradicted (framing: shifted — source metric is "% of infrastructure deployments done by LLMs" (~20%, projected 50%), while claim asserts "% of Pulumi's users" manage infrastructur…; evidence: Pulumi's own published figures cite a different metric and number: CEO Joe Duffy stated "LLMs are now doing over 20% of infrastructure deployments, up from virtually zero a year ago" and expects growth "to over 50% this year" — this is abo…; source: https://www.pulumi.com/releases/agentic-infrastructure-era/; intuition: The specific "40%" figure doesn't appear in any retrieved Pulumi source; the closest official stat (20%, trending to 50…)
L42 in content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md "With this release, stacks with Terraform state are first-class entities in Pulumi Cloud. They get access to all of the capabilities that organizations need to…" → ✅ verified (evidence: This is Pulumi's own first-party GA announcement; sibling docs corroborate that the Terraform state backend brings RBAC, audit policies, and other Pulumi Cloud capabilities to Terraform-backed stacks, e.g. "Pulumi Cloud can store Terraform…; source: gh search code --owner pulumi "terraform-state-backend" (pulumi/docs:content/docs/iac/comparisons/terraform/_index.md))
L44 in content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md "- Manage access to your Terraform stacks at scale using tag-based access control, team role assignments,…" → ✅ verified (evidence: The RBAC doc page confirms all three mechanisms: "tag-based (ABAC) rules" under Roles, "Team roles and entity access grants" section, and "User role" section describing per-user role assignment.; source: repo:content/docs/administration/access-identity/rbac/_index.md)
L46 in content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md "- Run preventive policies after a Terraform plan to block non-compliant resources before deployment." → ❌ contradicted (evidence: The blog claims you can "Run preventive policies after a Terraform plan to block non-compliant resources," but Pulumi's own docs on the Terraform state backend explicitly say the opposite: "Only audit (detective) policies are supported for…; source: repo:content/docs/iac/get-started/terraform/terraform-state-backend.md)
L47 in content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md "- Terraform state configuration is hosted natively in ESC, which lets you securely inject OIDC credentials at apply time and expose outputs to do…" → ✅ verified (evidence: The linked /docs/esc/ page describes ESC's "Login providers: Issue short-lived OIDC credentials for AWS, Azure, GCP, GitHub, and more" and "Use ESC with Pulumi IaC... Consume environments from a Pulumi program," supporting the claim that E…; source: repo:content/docs/esc/_index.md)
L48 in content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md "Pulumi Cloud as a Terraform state backend enables organizations to seamlessly lift and shift their existing Terraform estates." → ✅ verified (evidence: Docs and blog posts confirm Pulumi Cloud as a Terraform state backend: "Migrate your state in minutes — keep using the Terraform CLI while gaining encrypted state, RBAC, audit policies, and unified resource visibility across your entire in…; source: pulumi/docs:content/blog/terraform-state-backend-pulumi-cloud/index.md)
L50 in content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md "We recognize there is lots of infrastructure that works as is, and switching over to a new management paradigm may not always be possible. Pulumi Cloud support…" → ✅ verified (evidence: Corroborated by sibling docs: "Pulumi Cloud can serve as a Terraform state backend... letting you store and manage Terraform state alongside your Pulumi stacks. Your team can continue using the Terraform or OpenTofu CLI for day-to-day oper…; source: pulumi/docs:content/docs/iac/get-started/terraform/terraform-state-backend.md)
L51 in content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md "HashiCorp Configuration Language (HCL) is now generally available as a first-class language in Pulumi IaC. Just…" → ✅ verified (evidence: The blog's actual link at this location points to /docs/iac/languages-sdks/hcl/ (not the source_hint's convert-hcl path), which documents Pulumi HCL as a full language plugin: "Pulumi supports writing your infrastructure as code using Pulu…; source: pulumi/docs:content/docs/iac/languages-sdks/hcl/_index.md; pulumi/docs:content/blog/best-terraform-alternatives/index.md)
L52 in content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md "Pulumi Cloud's default remote plans/applies behavior for Terraform follows the behavior of HCP Terraform and Terraform Enterprise." → ✅ verified (evidence: The docs page confirms "Pulumi Cloud implements the Terraform remote backend API," the same standard remote backend protocol used by HCP Terraform/Terraform Enterprise, which are well known to default to remote plan/apply execution. The bl…; source: repo:content/docs/iac/get-started/terraform/terraform-state-backend.md; repo:content/blog/how-we-built-a-distributed-work-scheduling-system-for-pulumi-cloud/index.md)
L52 in content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md "Users get full visibility into Terraform operations run via Pulumi Cloud both on their local CLI and in the Pulumi Cloud console." → ✅ verified (evidence: Source text (same doc, line 52): "When you run a Terraform operation, it executes on a Pulumi-hosted runner rather than your local machine. You get full visibility into these operations both on your local CLI and in the Pulumi Cloud consol…; source: repo:content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md)
L53 in content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md "Production deployments may be gated with manual approvals before applying a Terraform plan in Pulumi Cloud." → 🤷 unverifiable (evidence: verification did not converge within 8 turns)
L55 in content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md "Stacks with Terraform state are first-class entities in Pulumi Cloud, with access to all the same capabilities as other Pulumi Cloud stacks." → ❌ contradicted (framing: narrowed — claim asserts "all the same capabilities" but the product's own reference doc documents that preventative policies are not applicable to Terraform-m…; evidence: The blog claims Terraform-state stacks get "access to all of the capabilities" of Pulumi Cloud stacks, but the linked reference doc (terraform-state-backend.md) explicitly carves out an exception: "Only audit (detective) policies are suppo…; source: repo:content/docs/iac/get-started/terraform/terraform-state-backend.md)
L57 in content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md "Pulumi programs, regardless of language, now support importing Terraform modules natively. Organizations…" → ✅ verified (evidence: The target doc content/docs/iac/get-started/terraform/terraform-modules.md exists and confirms this exact capability: "Pulumi can directly use existing Terraform modules from the Terraform Registry, private registries, or local sources...…; source: repo:content/docs/iac/get-started/terraform/terraform-modules.md)
L57 in content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md "Access to Terraform stacks at scale can be managed using tag-based access control." → ✅ verified (evidence: The RBAC docs page states roles can apply "tag-based (ABAC) rules" to entities including stacks: "The access rules in a role that apply to entities may be applied to all entities of that type, explicitly selected entities, or they can be t…; source: repo:content/docs/administration/access-identity/rbac/_index.md)
L58 in content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md "Neo code reviews are available for pull requests, leveraging what Pulumi Cloud knows about running infrastructure." → ✅ verified (evidence: The docs/blog page confirms: "Neo code reviews analyze pull request changes in conjunction with what Pulumi Cloud knows about your running infrastructure, providing both high-level and code-level feedback" (content/blog/neo-code-reviews/in…; source: gh search code --owner pulumi "code-reviews" --repo pulumi/docs)
L59-60 in content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md "Pulumi ESC can expose outputs to downstream stacks and services for Terraform deployments." → ✅ verified (evidence: Blog line 60 states ESC is used "to securely inject OIDC credentials at apply time and expose outputs to downstream stacks and services" for Pulumi Cloud-backed Terraform projects — this is the source of the claim itself, describing a firs…; source: repo:content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md#L60)
L59 in content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md "Preventive policies can be run after a Terraform plan to block non-compliant resources before deployment." → ✅ verified (evidence: The linked docs page states preventative policy enforcement "Validates Pulumi stack resources during pulumi preview and pulumi up, blocking deployments when violations are detected. Prevents non-compliant resources from being created."…; source: repo:content/docs/insights/policy/_index.md; repo:content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md)
L60 in content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md "- Configure your Terraform deployments with Pulumi ESC, which is natively available to Pulumi Cloud-backed Terraform projects, to securely in…" → ✅ verified (evidence: The /docs/esc/ link resolves to the ESC docs landing page, and the sibling terraform-state-backend doc corroborates native ESC integration for Terraform stacks: "Platform integration — root module outputs become Pulumi stack outputs, acc…; source: repo:content/docs/iac/get-started/terraform/terraform-state-backend.md)
L62 in content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md "There is a guide titled 'Using Pulumi Cloud as a Terraform state backend' available at /docs/iac/get-started/terraform/terraform-state-backend/." → ✅ verified (evidence: The page at content/docs/iac/get-started/terraform/terraform-state-backend/ exists with title "Store Terraform State in Pulumi Cloud" and content: "Pulumi Cloud can serve as a Terraform state backend... letting you store and manage Terrafo…; source: repo:content/docs/iac/get-started/terraform/terraform-state-backend.md)
L66 in content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md "HCL in Pulumi is 100% OpenTofu compatible with no syntactical differences." → ✅ verified (evidence: Pulumi's own comparison page confirms HCL support in Pulumi uses the same configuration language as OpenTofu: "The same flag handles both Terraform and OpenTofu HCL — there is no separate --from opentofu flag, because the configuration lan…; source: https://www.pulumi.com/docs/iac/comparisons/opentofu/)
L66 in content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md "Because of Pulumi's Terraform bridge, any existing Terraform provider works with HCL in Pulumi." → ✅ verified (evidence: Blog source at L66 states: "Thanks to our Terraform bridge, if there's a Terraform provider out there, it just works." The sibling HCL docs page corroborates: "providers resolve against the OpenTofu registry and are bridged into Pulumi aut…; source: repo:content/docs/iac/languages-sdks/hcl/_index.md)
L66 in content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md "HCL as a Pulumi language has full access to the entirety of the Pulumi ecosystem, including thousands of providers." → ✅ verified (evidence: The HCL docs page states providers "resolve against the OpenTofu registry and are bridged into Pulumi automatically" and that "The Pulumi Registry also houses 100+ native Pulumi packages," confirming HCL has access to the full Pulumi ecosy…; source: repo:content/docs/iac/languages-sdks/hcl/_index.md)
L66 in content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md "- A free IaC modernization workshop. Our professional services cloud architects host a free IaC modernization workshop to review where you're at with your…" → ✅ verified (evidence: A prior Pulumi blog post states nearly identical language: "Our professional services cloud architects will host a free IaC modernization workshop to review where you're at with your IaC already and share best practices of how to adopt the…; source: https://www.pulumi.com/blog/all-iac-including-terraform-and-hcl/ ; https://www.pulumi.com/case-studies/bmw/)
L70 in content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md "There is an HCL language reference available at /docs/iac/languages-sdks/hcl/." → ✅ verified (evidence: content/docs/iac/languages-sdks/hcl/_index.md exists at path /docs/iac/languages-sdks/hcl/ and serves as "Pulumi & HCL" overview page, linking further to the "Pulumi HCL reference" at /docs/iac/languages-sdks/hcl/hcl-language-reference/.; source: repo:content/docs/iac/languages-sdks/hcl/_index.md)
L73 in content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md "The agentic infrastructure era is already here, and we want you to bring your IaC to it. Get started with Pulumi free and provision your firs…" → ✅ verified (evidence: /docs/install/ resolves to the Pulumi "Download & Install Pulumi" page, which states Pulumi Cloud is "free for individuals ... no credit card required," supporting the "Get started with Pulumi free" link text and target.; source: repo:content/docs/install/_index.md)
L74 in content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md "Organizations can leverage existing reusable Terraform module artifacts as-is without making a single change, using Pulumi's native Terraform module import." → ✅ verified (evidence: The pulumi/docs page content/docs/iac/get-started/terraform/terraform-modules.md states: "Pulumi can directly use existing Terraform modules from the Terraform Registry, private registries, or local sources. This allows you to access thous…; source: gh api repos/pulumi/docs/contents/content/docs/iac/get-started/terraform/terraform-modules.md)
L74 in content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md "Pulumi programs, regardless of language, now support importing Terraform modules natively." → ✅ verified (evidence: pulumi/pulumi-terraform-module README states: "This provider supports running Terraform Modules directly in Pulumi... Pulumi will generate a local SDK in your current programming language and print instructions on how to use it," with expl…; source: gh api repos/pulumi/pulumi-terraform-module/contents/README.md)
L75 in content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md "If you'd like to get started with the new Terraform/OpenTofu and HCL capabilities, or take advantage of the financial flexibility options, please [get in touch…" → ✅ verified (evidence: The page at https://www.pulumi.com/contact/?form=sales exists and states: "Contact Pulumi for any general inquiries, including requests for pricing, support, or training."; source: https://www.pulumi.com/contact/?form=sales)
L76 in content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md "Terraform modules hosted in Pulumi Cloud can be used in both Pulumi and Terraform programs." → 🤷 unverifiable (evidence: verification did not converge within 8 turns)
L78 in content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md "There is a guide titled 'Using Terraform modules in Pulumi' available at /docs/iac/get-started/terraform/terraform-modules/." → ✅ verified (framing: strengthened — claim paraphrases the page title ("Import Terraform Modules") as "Using Terraform modules in Pulumi"; same page/topic, URL matches exactly.; evidence: The file content/docs/iac/get-started/terraform/terraform-modules.md exists and renders at /docs/iac/get-started/terraform/terraform-modules/, with title "Import Terraform Modules" and content "Pulumi can directly use existing Terraform mo…; source: repo:content/docs/iac/get-started/terraform/terraform-modules.md)
L82 in content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md "Pulumi made a promise last December regarding not making customers pay for two IaC solutions." → ✅ verified (evidence: Pulumi's blog post dated December 18, 2025 states: "The last thing we want is for you to have to pay for two IaC solutions for a period of time," and further offers credit transfers "avoiding double pay."; source: https://www.pulumi.com/blog/all-iac-including-terraform-and-hcl/)
L84 in content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md "Customers can apply credits purchased from HashiCorp toward their Pulumi usage until their next renewal." → 🤝 matches (evidence: The blog body itself states: "we're letting you apply credits purchased from HashiCorp toward your Pulumi usage until your next renewal, avoiding double pay" — this is Pulumi's own first-party program description, and the claim text is a f…; source: repo:content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md L84)
L85 in content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md "Pulumi's professional services cloud architects have worked with organizations including BMW, Modular, and Supabase to help them adopt the Pulumi platform at s…" → 🤷 unverifiable (evidence: Pulumi publicly confirms BMW and Supabase as major customers/case studies (e.g. "Join Snowflake, Supabase, BMW, and leading AI companies managing production-ready infrastructure at massive scale"), but no public Pulumi case study or refere…; source: https://www.pulumi.com/product/superintelligence-infrastructure/ (WebSearch dispatched but verification did not converge within the turn budget))
L85 in content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md "Pulumi has worked with Supabase on IaC adoption at scale." → ✅ verified (evidence: Pulumi's official case study describes Supabase's large-scale IaC adoption with Pulumi, including scaling to 16 AWS regions and ~80,000 resources: "now serving customers across 16 AWS regions and managing approximately 80,000 Pulumi resour…; source: https://www.pulumi.com/case-studies/supabase/)
L86 in content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md "Pulumi offers a return on investment (ROI) calculation showing that moving to Pulumi will be spend-neutral thanks to the escape hatch." → ➖ not-a-claim (evidence: Line 86 of the same document reads: "A return on investment (ROI) calculation. We will show you how the move to Pulumi will not only be spend-neutral thanks to the escape hatch, but how much value and savings you should expect to see..." — this is the PR author's own first-party description of their own program/offering, not a third-party-attributed factual claim requiring external verification.; source: repo:content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md)
L86 in content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md "Pulumi helped Snowflake accelerate its time to market, going from code to cloud in weeks down to hours." → ✅ verified (framing: strengthened — claim says "weeks down to hours" while source specifically states "a week and a half" down to "under a day"; close paraphrase, slightly rounds the framing but directionally accurate.; evidence: Pulumi's Snowflake case study quotes Raman Hariharan: "When we demonstrated to people that what used to take a week and a half now, with Pulumi, took under a day, they were shocked." This supports "weeks down to hours/under a day" though the case study says "under a day" rather than literally "hours."; source: https://www.pulumi.com/case-studies/snowflake/)
L86 in content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md "Snowflake went from code to cloud in hours, down from weeks, with Pulumi's help." → ❌ contradicted (framing: narrowed/shifted — claim rounds 'a week/week-and-a-half to under a day' into 'weeks to hours'; source specifies single-day turnaround, not multi-hour, and only one deployment scenario, not a general 'weeks' baseline; evidence: The Pulumi Snowflake case study quotes Raman Hariharan: "if we had gone down the traditional infrastructure automation route, it would have taken us a week or a week and a half to do one deployment... what used to take a week and a half now, with Pulumi, took under a day." The actual figures are 'a week/week and a half' down to 'under a day' — not the broader 'weeks' down to 'hours' claimed in the blog.; source: https://www.pulumi.com/case-studies/snowflake/)
L88 in content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md "Pulumi's offers are available to customers of all sizes in all industries, whether a Global 2000, a startup, or somewhere in between." → ➖ not-a-claim (evidence: This is a marketing/positioning statement about Pulumi's general market availability, not a falsifiable technical or factual claim that can be verified against product source or documentation.; source: content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md L88)
L88 in content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md "Pulumi's escape hatch, workshop, and ROI offers together ensure there is no financial penalty for switching, a very clear ROI, and no learning curve." → ✅ verified (evidence: The Pulumi blog post "Pulumi for All Your IaC — Including Terraform and HCL" states verbatim: "These ensure there's no financial penalty for switching, a very clear ROI, and no learning curve," referring to the escape hatch, workshop/exper…; source: https://www.pulumi.com/blog/all-iac-including-terraform-and-hcl/)
L92 in content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md "Users can get started with Pulumi for free at https://app.pulumi.com/signup." → ✅ verified (evidence: The cited URL https://app.pulumi.com/signup returns HTTP 200 and loads the Pulumi Cloud signup page, consistent with the claim that users can sign up there; free tier availability is a well-established Pulumi Cloud offering.; source: https://app.pulumi.com/signup)

📊 Editorial balance

Single-subject post; balance check N/A.

🚨 Outstanding in this PR

These must be resolved or refuted before merging.

[L27] content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md — "Remote plans and applies work against existing Terraform stacks via Pulumi Cloud." — verdict: contradicted; framing: shifted — blog claims "remote plans and applies... execute on a Pulumi-hosted runner"; the sibling docs page for the same feature says operations continue via…; evidence: The blog claims "Plans and applies run remotely by default... it executes on a Pulumi-hosted runner rather than your local machine," but the linked implementing docs page (content/docs/iac/get-started/terraform/terraform-state-backend.md)…; source: repo:content/docs/iac/get-started/terraform/terraform-state-backend.md; intuition: Blog's "remote runner" framing for a feature documented elsewhere as purely a state backend (local CLI execution) is su… — Author question, and the highest-priority one in this review. The docs page for this feature reads two different ways depending on which passage you land on: one part says Pulumi Cloud "implements the Terraform remote backend API" (which would default to remote execution, matching the post — this is why the L52 claim came back ✅ verified), and another says teams "continue using the Terraform or OpenTofu CLI for day-to-day operations" locally. Both the body (line 52, "it executes on a Pulumi-hosted runner rather than your local machine") and the LinkedIn copy (line 27, "remote plans and applies, manual approvals, RBAC, and Neo code reviews all work against your existing Terraform stacks") assert the remote-runner behavior unconditionally. Please confirm with the feature team whether remote execution is GA at this post's publish date, and if it is gated or opt-in, qualify both places. This one is called out first because the social.linkedin copy auto-posts to LinkedIn on merge — an overstatement there can't be quietly edited afterward the way the post body can. If remote execution is GA as written, say so on the PR and the docs page should be updated to match, not the post.
[L38] content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md — "Over 40% of Pulumi's users now manage infrastructure using AI agents." — verdict: contradicted; framing: shifted — source metric is "% of infrastructure deployments done by LLMs" (~20%, projected 50%), while claim asserts "% of Pulumi's users" manage infrastructur…; evidence: Pulumi's own published figures cite a different metric and number: CEO Joe Duffy stated "LLMs are now doing over 20% of infrastructure deployments, up from virtually zero a year ago" and expects growth "to over 50% this year" — this is abo…; source: https://www.pulumi.com/releases/agentic-infrastructure-era/; intuition: The specific "40%" figure doesn't appear in any retrieved Pulumi source; the closest official stat (20%, trending to 50… — Two things differ from every published Pulumi figure found: the number (40% vs. the 20%-trending-to-50% that Pulumi has consistently cited) and the unit (share of users vs. share of deployments). If 40%-of-users is a newer internal metric, that's fine — but it needs to be the number the company is standing behind publicly, and the unit should be stated so readers don't read it as a restatement of the deployments stat.
```
At Pulumi, we are building the platform for agentic infrastructure. Pulumi Cloud provides the guardrails and enterprise readiness needed to safely move fast in this new era. While we are seeing extraordinary adoption — LLMs now drive over 20% of infrastructure deployments, up from virtually zero a year ago — we know many organizations are at different phases in their AI journey and have to balance building for the future with maintaining their existing infrastructure as code (IaC) solutions like Terraform. Today, we are launching three ways that Pulumi lets you avoid trading off building for the future against building for today. You don't have to rip out Terraform to enter the agentic era — Pulumi Cloud brings agentic infrastructure to the IaC estate you already have.
```
Swap in the 40%-of-users figure instead if you can point to where it's published or cleared for publication.
[L46] content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md — "- Run preventive policies after a Terraform plan to block non-compliant resources before deployment." — verdict: contradicted; evidence: The blog claims you can "Run preventive policies after a Terraform plan to block non-compliant resources," but Pulumi's own docs on the Terraform state backend explicitly say the opposite: "Only audit (detective) policies are supported for…; source: repo:content/docs/iac/get-started/terraform/terraform-state-backend.md — This is the bullet at line 59 of the file (the verification step anchored it to the frontmatter copy of the same sentence). The Terraform state backend docs carve this out explicitly: only audit (detective) policies apply to Terraform-managed resources, so "block non-compliant resources before deployment" promises enforcement a reader can't get today. Either scope the bullet to detective policies or, if preventive enforcement shipped with this release, update the docs page in the same PR so the two agree.
```
- [**Run compliance policies**](/docs/insights/policy/) against your Terraform resources to detect non-compliant infrastructure and report violations.
```
[L55] content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md — "Stacks with Terraform state are first-class entities in Pulumi Cloud, with access to all the same capabilities as other Pulumi Cloud stacks." — verdict: contradicted; framing: narrowed — claim asserts "all the same capabilities" but the product's own reference doc documents that preventative policies are not applicable to Terraform-m…; evidence: The blog claims Terraform-state stacks get "access to all of the capabilities" of Pulumi Cloud stacks, but the linked reference doc (terraform-state-backend.md) explicitly carves out an exception: "Only audit (detective) policies are suppo…; source: repo:content/docs/iac/get-started/terraform/terraform-state-backend.md — Same root cause as the L46 finding, in the framing sentence rather than the bullet. "All of the capabilities" is an absolute a documented exception already breaks, and it's the sentence a skeptical Terraform reader will hold you to. Naming the capabilities is also stronger copy than claiming totality — and it clears the all of wordiness nag on this line.
```
With this release, stacks with Terraform state are first-class entities in Pulumi Cloud, with access to the platform capabilities organizations need to scale in this new AI-first era.
```
[L86] content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md — "Snowflake went from code to cloud in hours, down from weeks, with Pulumi's help." — verdict: contradicted; framing: narrowed/shifted — claim rounds 'a week/week-and-a-half to under a day' into 'weeks to hours'; source specifies single-day turnaround, not multi-hour, and only…; evidence: The Pulumi Snowflake case study quotes Raman Hariharan: "if we had gone down the traditional infrastructure automation route, it would have taken us a week or a week and a half to do one deployment... what used to take a week and a half no…; source: https://www.pulumi.com/case-studies/snowflake/ — The Snowflake case study quotes Raman Hariharan on "a week and a half" becoming "under a day" for one deployment. "Weeks to hours" rounds both ends outward. Customer-attributed numbers should track the case study exactly — Snowflake reviewed those words, not these.
```
- **A return on investment (ROI) calculation.** We will show you how the move to Pulumi will not only be spend-neutral thanks to the escape hatch, but how much value and savings you should expect to see, given our experience helping innovators like Snowflake accelerate their time to market — taking a deployment that used to run a week and a half down to under a day.
```

⚠️ Low-confidence

Review each and resolve as appropriate — these don't block the PR.

[L53] content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md — "Production deployments may be gated with manual approvals before applying a Terraform plan in Pulumi Cloud." — verdict: unverifiable; evidence: verification did not converge within 8 turns — Author question: is the manual-approval gate for Terraform applies available at GA, and is it documented anywhere a reader can follow up? Nothing was found confirming or denying it, and it appears in the LinkedIn copy (line 27) as well as the body, so it's worth a second pair of eyes given that two neighboring capability claims on this same feature did come back contradicted. A link to the relevant docs section would settle it.
[L76] content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md — "Terraform modules hosted in Pulumi Cloud can be used in both Pulumi and Terraform programs." — verdict: unverifiable; evidence: verification did not converge within 8 turns — Author question: can a module published to the Pulumi Cloud private registry really be consumed from an HCL/Terraform program as a module source today, or is the bidirectional part forward-looking? "Maximum interoperability" reads as a shipped guarantee. If it works, a docs link here would both back the claim and give readers the next step; the paragraph currently ends without one.
[L85] content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md — "Pulumi's professional services cloud architects have worked with organizations including BMW, Modular, and Supabase to help them adopt the Pulumi platform at s…" — verdict: unverifiable; evidence: Pulumi publicly confirms BMW and Supabase as major customers/case studies (e.g. "Join Snowflake, Supabase, BMW, and leading AI companies managing production-ready infrastructure at massive scale"), but no public Pulumi case study or refere…; source: https://www.pulumi.com/product/superintelligence-infrastructure/ (WebSearch dispatched but verification did not converge within the turn budget) — BMW and Supabase are both public case studies, so those are safe. Modular isn't — no public case study or reference was found. Please confirm Modular is cleared as a named reference for professional-services engagement specifically; if it isn't, drop the name (BMW and Supabase carry the sentence fine).

Style findings

Found by pattern-based linting; Findings may be false positives.

line 38: [style] em-dash density — Heavy em-dash use in this paragraph (more than 2). Dense em-dash usage is often associated with AI-drafted prose; consider substituting commas or periods where it doesn't change emphasis.
line 44: [style] wordiness — 'all of' is too wordy.
line 55: [style] wordiness — 'all of' is too wordy.
line 66: [style] difficulty qualifier — Avoid difficulty qualifier 'Just' -- it judges difficulty for the reader (STYLE-GUIDE.md §Inclusive Language).
line 66: [style] difficulty qualifier — Avoid difficulty qualifier 'just' -- it judges difficulty for the reader (STYLE-GUIDE.md §Inclusive Language).
line 68: [style] difficulty qualifier — Avoid difficulty qualifier 'easily' -- it judges difficulty for the reader (STYLE-GUIDE.md §Inclusive Language).
line 68: [style] wordiness — 'all of' is too wordy.

github-actions · 2026-07-31T21:25:20Z

📋 Triaged verifier findings

I double-checked these and realized they weren't real findings — click to expand

[L25] content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md — "At Pulumi, we are building the platform for agentic infrastructure. Pulumi Cloud provides the guardrails and enterprise readiness needed to safely move fast in…" — verdict: contradicted; source: https://www.pulumi.com/releases/agentic-infrastructure-era/ — Spurious: this is the same "over 40% of our users" figure already tracked as the L38 finding, counted a second time because the opening paragraph was captured whole here (and anchored to the LinkedIn copy rather than to the body line). Fixing L38 resolves it.

💡 Pre-existing issues in touched files (optional)

No pre-existing issues in touched files.

✅ Resolved since last review

No items resolved since the last review.

📜 Review history

2026-07-31T21:19:35Z — Five blockers on a new Terraform-interop launch post: unpublished "40% of users" stat, preventive-policy and "all of the capabilities" overreach on Terraform-backed stacks, a remote-execution claim that conflicts with the feature's own docs (and rides the auto-posting LinkedIn copy), and a rounded Snowflake metric; plus three capability claims that need author confirmation. (01fdc62)

Need a re-review? Want to dispute a finding? Mention @claude and include #update-review.
(For ad-hoc questions or fixes, just @claude — no hashtag.)

djperlovsky · 2026-07-31T21:33:09Z

@claude #update-review — disputing all three outstanding findings. They share one root cause: the review verified against master, but these are new capabilities shipping 8/4, documented in a companion PR that hasn't merged yet.

[L46] Preventive policies — refuted. #20570 adds content/docs/iac/get-started/terraform/terraform-remote-execution.md, which states: "Policy enforcement — preventative policies evaluate against the plan and block applies that violate policy." The master text the review cited ("Only audit (detective) policies are supported") is what #20570 supersedes. The post's bullet is correct as written.

[L27] Remote execution — refuted. Same PR: "New stacks created through the Terraform or OpenTofu CLI default to remote execution. For existing stacks, set the terraform:execution-mode stack tag to remote." Remote-by-default is the shipping behavior, so both the body and the LinkedIn copy are accurate.

Manual approvals (raised in the summary) are likewise documented there: "By default, VCS-triggered applies pause after the plan completes and wait for manual approval before proceeding."

[L38] The 40% figure is confirmed by the author as current and cleared for this post. It is a distinct metric from the published "20% of infrastructure deployments" stat — share of users, not share of deployments — not a restatement of it.

Since the docs for these capabilities land in #20570, the two PRs should be reviewed as a pair; verifying this post against master alone will keep producing these same three findings.

🤖 Filed by Claude Code

Leaves BMW and Supabase as the named examples. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Per the companion docs PR (#20570), new stacks created through the Terraform or OpenTofu CLI default to remote execution; existing stacks enable it with a stack tag. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Drops "existing" so the claim holds for both new stacks (remote by default) and existing ones (remote via stack tag). Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

- Drop the third em dash in the intro (Pulumi.EmDashDensity); the intro is the excerpt shown on the blog index - Remove difficulty qualifiers "just like" and "easily" (Pulumi.Difficulty, STYLE-GUIDE.md Inclusive Language) - Drop the weasel "very" from "a very clear ROI" Keeps "it just works" — an idiom about the provider bridge, not a judgment about the reader's effort. Remaining warnings are generic write-good wordiness hits, left as-is. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

github-actions · 2026-07-31T21:57:51Z

🤖 Review updated on @djperlovsky's request.

Co-Authored-By: Claude <noreply@anthropic.com>

@cnunciato

* Blog: "Emulating Terraform on Pulumi's Engine" (#20573) * Draft 0 - half way done * Update feature image for Terraform data model blog post Co-Authored-By: Claude <noreply@anthropic.com> * Draft 1: complete (mostly) * links * Fill in hook mapping table, permalinks, and conclusion Fill the provisioner/condition-to-hook mapping table from the pulumi-hcl source, and correct the replace_triggered_by bullet to match the code: every element feeds replacementTrigger, and resource references also contribute to replaceWith. Replace the illustrative workspace.PackageDescriptor snippets with the pulumirpc.PackageSpec requests that are actually sent, and link to the request-construction code in pulumi-hcl and the latest-version resolution code in the dynamic bridge. Add the concluding section: thesis restated, known gaps, and a call to action to file compatibility issues. * Address review: fix SDK namespace, MLC link, and conclusion typo Use the pulumi namespace in all module-consumption examples; the SDK publishes under pulumi, not pulumi-labs. Point the multi-language components link at its real path under guides/building-extending. Fix a misspelling and missing serial comma in the conclusion. * Bind the precondition hook to beforeUpdate as well Match the TypeScript equivalence example to the mapping table: preconditions run on both create and update. --------- Co-authored-by: Jeff Merrick <jmerrick@pulumi.com> Co-authored-by: Claude <noreply@anthropic.com> * blog: add "Bring Your Terraform Estate Into the Agentic Era" launch post (#20569) * blog: add "Bring Your Terraform Estate Into the Agentic Era" launch post Staged for publication on 2026-08-04 at 9:00 AM Pacific. Announces the GA of Pulumi Cloud as a Terraform state backend, HCL as a first-class Pulumi IaC language, and native Terraform module support, along with the continued HashiCorp transition offers. Follows on from Joe Duffy's December post, "Pulumi for All Your IaC — Including Terraform and HCL," and links back to it as the setup. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * blog: render 1884x1256 rocket feature image The shared placeholder copied by /new-blog-post is 942x628, which fails the markdown linter's feature-image dimension check. Replace it with a rocket template render (the launch/announcement template) at the required 1884x1256. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * blog: add social copy for the Terraform launch post Fills the blank twitter/linkedin/bluesky frontmatter fields with the copy drafted by the social-review check. All three tee up the post without delivering the announcement, and deliberately omit the "over 40% of users" stat pending a freshness check before the Aug 4 publish date. X 235/255, LinkedIn 692/2950, Bluesky 259/300. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * blog: apply review feedback from @cnunciato Copy edits for parallelism and clarity in the Terraform backend bullets, plus: - Reframe the interop claim as "Pulumi is now fully interoperable with Terraform and OpenTofu" - Note that remote-by-default plans/applies follow HCP Terraform and Terraform Enterprise behavior - Point the HCL link at the HCL language docs rather than the convert guide - Add a "learn more" docs link at the end of each of the three capability sections - Link "Get started with Pulumi free" to app.pulumi.com/signup Two review questions are left for the author: whether to move the modules section ahead of HCL, and whether to link out to Christian's forthcoming getting-started post. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * blog: reorder to backend, modules, then HCL Per review feedback, the three capability sections now follow an adoption progression: bring state to Pulumi Cloud, reuse the modules you already have, then write HCL natively. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * blog: drop Modular from the workshop customer list Leaves BMW and Supabase as the named examples. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * blog: scope remote-by-default to new Terraform stacks Per the companion docs PR (#20570), new stacks created through the Terraform or OpenTofu CLI default to remote execution; existing stacks enable it with a stack tag. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * blog: align LinkedIn copy with remote-execution scoping Drops "existing" so the claim holds for both new stacks (remote by default) and existing ones (remote via stack tag). Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * blog: address prose-lint warnings - Drop the third em dash in the intro (Pulumi.EmDashDensity); the intro is the excerpt shown on the blog index - Remove difficulty qualifiers "just like" and "easily" (Pulumi.Difficulty, STYLE-GUIDE.md Inclusive Language) - Drop the weasel "very" from "a very clear ROI" Keeps "it just works" — an idiom about the provider bridge, not a judgment about the reader's effort. Remaining warnings are generic write-good wordiness hits, left as-is. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * blog: update feature image for Terraform estate post Co-Authored-By: Claude <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5 <noreply@anthropic.com> Co-authored-by: Jeff Merrick <jmerrick@pulumi.com> * Add walkthrough blog covering state backend, modules, and HCL (#20644) * blog: add hands-on Terraform/HCL/Pulumi Cloud walkthrough (draft) Companion walkthrough for the HCL Launch campaign (publishing 2026-08-04): migrate Terraform state to the Pulumi Cloud backend, publish and consume a Terraform module via the Pulumi Cloud registry, and write HCL that runs natively on the Pulumi engine. Draft: still needs 3 screenshots, a feature image, and social copy. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * blog: add feature image for the Terraform/Pulumi Cloud walkthrough Co-Authored-By: Claude <noreply@anthropic.com> * blog: answer reader questions with brief inline notes and links Completeness pass on the Terraform/HCL walkthrough: - Link the launch announcement post from the intro. - Migration: back up state first, reassure that only state location changes, and link out for S3/Azure/GCS/HCP/TFE source backends. - Note audit policies (every stack) vs preventative policies (remote runs). - Link the Terraform module registry concept page. - Point HCL readers at `pulumi convert` for moving to a general-purpose language on their own schedule. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * blog: sharpen framing and fix doc links per author review - Reframe the intro around the three buckets (state backend + remote execution, modules as cross-language Pulumi components, first-class HCL), lead with GA, and pitch it as a brisk end-to-end walkthrough doable with a free account and trial. Link the release page and the announcement post. - Develop the "why HCL": native pulumi/ providers alongside bridged ones, cross-language component/module interop, and the superset point, linking Ian's engine deep-dive. - Sharpen the "why a dynamic module" note. - Warmer open-source (Apache 2.0) close inviting issues and feedback. - Fix dead link /docs/idp/deployments/ -> /docs/deployments/, and soften "audit policies run on every stack" to "can run on any stack." Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * blog: apply docs-review fixes (acronyms, org context, product name) - Expand HCL and Pulumi ESC on first mention. - Note the module work happens in a separate org from the migrated personal account, to avoid org-context confusion. - Capitalize the product name "Pulumi Policies". Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * blog: feature the Terraform launch posts on the homepage Pin the homepage featured slots for the Aug 4 launch: the "Bring Your Terraform Estate Into the Agentic Era" announcement as the hero, followed by the "Emulating Terraform on Pulumi's Engine" deep-dive and this hands-on walkthrough. Slot 4 auto-fills. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * Revisions * blog: copyedit pass, fix ESC link, tighten deployments steps - Fix dropped-word typos (consume, some teams, seen, a/an) and a broken relative ESC link (add leading slash). - Add descriptive alt text to all four screenshots. - Reword the HCL provider/module line (no "community-supported hashicorp/*"; don't conflate providers with modules). - Tighten the VCS/Deployments walkthrough from four steps to three, keeping every action and the confirm screenshot. - Normalize all shell command lines to a $ prompt for consistency. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * Almost there * blog: typo and grammar scrub Fix dropped/incorrect words (a locally defined module, terraform CLI, workspace name, paste into the prompt, copy your existing state, create a new project), a stray comma, and a doubled phrase in the closing links. Drop the contradictory "bridged" qualifier on the pulumi/aws provider and fix the "community-supported" typo. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * blog: cross-link the three Terraform launch posts as related Add mutual related_posts entries so the launch, engineering, and walkthrough posts each surface the other two in their Related posts block. Also fix a "sign into" -> "sign in to" typo in the walkthrough and tidy the featured-slot comments in blog_home.yaml. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * Meta --------- Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com> Co-authored-by: Jeff Merrick <jmerrick@pulumi.com> * Add the August 2026 Terraform and HCL release page (#20617) * Add the August 2026 Terraform and HCL release page Adds /releases/terraform-and-hcl/, a smaller launch page covering the three capabilities announced in the Terraform/HCL launch post: Pulumi Cloud as a Terraform state backend, HCL as a first-class Pulumi language, and native Terraform module support. Every card traces to that post; the page reuses the existing releases layout, so it's frontmatter-only apart from the two partial changes below. Dated 2026-08-04 to match the launch post, so it won't build until then. Extends layouts/partials/releases/hero-card.html with an optional hero_image_max_height, which sizes hero art by height instead of width. The May page's hero is square (427x433) while this one is wide (761x419), so a shared max-width rendered the new art at roughly half the height. The heading now also renders as raw HTML so a <br> can control where it wraps. Fixes three layout issues in layouts/partials/releases/release-item.html that affect every card on /releases/: the feature image was flush to the card's left edge on mobile, images were vertically centered rather than sitting on the card's bottom edge, and cards with differently-proportioned artwork came out at different heights. The image column now holds a fixed 600/497 aspect, so cards line up at any viewport width rather than at one fixed breakpoint. Co-Authored-By: Claude <noreply@anthropic.com> * Update the Terraform and HCL release feature image Swaps in revised artwork for the /releases/ list card. Same 600x399 viewBox as before, so the card layout is unaffected. Co-Authored-By: Claude <noreply@anthropic.com> * Rename the Terraform and HCL release page slug Moves the page to /releases/terraform-state-backend-modules-hcl/, naming the three shipped capabilities directly. No alias needed: the page is future-dated and unmerged, so the old URL has never been live and nothing links to it. Co-Authored-By: Claude <noreply@anthropic.com> * Add the social card for the Terraform and HCL release page Adds the hand-made 1200x628 card and points meta_image at it. Lives under static/ rather than assets/fingerprinted/, since a non-blog meta_image resolves as a raw path. Co-Authored-By: Claude <noreply@anthropic.com> * Reorder release sections (modules before HCL) and point homepage badge at the release page Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * Add launch banner for the Terraform state, modules, and HCL release Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * Swap access-control card for remote execution and refine release copy Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * Finalize release page: module and HCL cards, copy fixes, badge, and banner Adds module and HCL cards to the August 2026 release page, links the newly-landed walkthrough post, and applies a copy/typo pass. Updates the homepage badge and launch-banner text to match. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * Refine release hero description copy Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> --------- Co-authored-by: Claude <noreply@anthropic.com> Co-authored-by: Christian Nunciato <chris@nunciato.org> * Use @pulumi/hcl and pulumi/pulumi-hcl as canonical HCL references Update the Terraform-to-Pulumi-Cloud walkthrough to install and import the @pulumi/hcl package (the labs-scoped @pulumi-labs/hcl has graduated to the @pulumi scope), so it agrees with the engineering deep-dive post. Also correct the docs-review verify-claims reference: Pulumi HCL now lives under pulumi/pulumi-hcl, not pulumi-labs/pulumi-hcl. Point-in-time -labs references in existing blog posts are left as-is. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> --------- Co-authored-by: Ian Wahbe <me@iwahbe.com> Co-authored-by: Jeff Merrick <jmerrick@pulumi.com> Co-authored-by: Claude <noreply@anthropic.com> Co-authored-by: Daniel Perlovsky <dperlovsky@pulumi.com>

djperlovsky had a problem deploying to testing July 29, 2026 21:03 — with GitHub Actions Failure

djperlovsky had a problem deploying to production July 29, 2026 21:03 — with GitHub Actions Error

djperlovsky temporarily deployed to testing July 29, 2026 21:10 — with GitHub Actions Inactive

djperlovsky temporarily deployed to production July 29, 2026 21:10 — with GitHub Actions Inactive

djperlovsky requested a review from cnunciato July 29, 2026 21:13

djperlovsky temporarily deployed to production July 29, 2026 21:18 — with GitHub Actions Inactive

djperlovsky temporarily deployed to testing July 29, 2026 21:18 — with GitHub Actions Inactive

cnunciato added the needs-design label Jul 30, 2026

cnunciato approved these changes Jul 30, 2026

View reviewed changes

djperlovsky temporarily deployed to testing July 30, 2026 23:44 — with GitHub Actions Inactive

djperlovsky temporarily deployed to production July 30, 2026 23:44 — with GitHub Actions Inactive

jeffmerrick mentioned this pull request Jul 31, 2026

Add the August 2026 Terraform and HCL release page #20617

Merged

djperlovsky marked this pull request as ready for review July 31, 2026 21:16

djperlovsky temporarily deployed to production July 31, 2026 21:16 — with GitHub Actions Inactive

github-actions Bot added review:triaging Claude Triage is currently classifying the PR domain:blog PR touches blog posts or customer stories review:in-progress Claude review is currently running and removed review:triaging Claude Triage is currently classifying the PR labels Jul 31, 2026

blog: reorder to backend, modules, then HCL

2392b51

Per review feedback, the three capability sections now follow an adoption progression: bring state to Pulumi Cloud, reuse the modules you already have, then write HCL natively. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

djperlovsky temporarily deployed to testing July 31, 2026 21:25 — with GitHub Actions Inactive

djperlovsky temporarily deployed to production July 31, 2026 21:25 — with GitHub Actions Inactive

github-actions Bot added the review:outstanding-issues Claude review completed; outstanding has author-actionable findings label Jul 31, 2026

github-actions Bot added review:in-progress Claude review is currently running and removed review:outstanding-issues Claude review completed; outstanding has author-actionable findings labels Jul 31, 2026

blog: drop Modular from the workshop customer list

eb5c7b5

Leaves BMW and Supabase as the named examples. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

djperlovsky temporarily deployed to testing July 31, 2026 21:34 — with GitHub Actions Inactive

djperlovsky had a problem deploying to production July 31, 2026 21:34 — with GitHub Actions Error

blog: scope remote-by-default to new Terraform stacks

8fdff0e

Per the companion docs PR (#20570), new stacks created through the Terraform or OpenTofu CLI default to remote execution; existing stacks enable it with a stack tag. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

djperlovsky temporarily deployed to testing July 31, 2026 21:36 — with GitHub Actions Inactive

djperlovsky had a problem deploying to production July 31, 2026 21:36 — with GitHub Actions Error

blog: align LinkedIn copy with remote-execution scoping

53569f5

Drops "existing" so the claim holds for both new stacks (remote by default) and existing ones (remote via stack tag). Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

djperlovsky temporarily deployed to testing July 31, 2026 21:39 — with GitHub Actions Inactive

djperlovsky temporarily deployed to production July 31, 2026 21:39 — with GitHub Actions Inactive

djperlovsky temporarily deployed to testing July 31, 2026 21:46 — with GitHub Actions Inactive

djperlovsky temporarily deployed to production July 31, 2026 21:46 — with GitHub Actions Inactive

cnunciato mentioned this pull request Aug 2, 2026

Add walkthrough blog covering state backend, modules, and HCL #20644

Merged

4 tasks

blog: update feature image for Terraform estate post

1ce6db8

Co-Authored-By: Claude <noreply@anthropic.com>

jeffmerrick temporarily deployed to production August 3, 2026 16:28 — with GitHub Actions Inactive

jeffmerrick temporarily deployed to testing August 3, 2026 16:28 — with GitHub Actions Inactive

cnunciato changed the base branch from master to release/2026-08-04 August 3, 2026 18:43

cnunciato merged commit f7c7133 into release/2026-08-04 Aug 3, 2026
11 checks passed

cnunciato deleted the djperlovsky/pull-master-changes-cb1a8d branch August 3, 2026 23:29

cnunciato temporarily deployed to testing August 3, 2026 23:29 — with GitHub Actions Inactive


		The agentic infrastructure era is already here, and we want you to bring your IaC to it. [Get started with Pulumi free](/docs/install/) and provision your first stack in minutes.

		If you'd like to get started with the new Terraform/OpenTofu and HCL capabilities, or take advantage of the financial flexibility options, please [get in touch](/contact/?form=sales).

Uh oh!

Conversation

djperlovsky commented Jul 29, 2026 • edited by cnunciato Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Proposed changes

Related PRs

Notes for reviewers

Uh oh!

github-actions Bot commented Jul 29, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Social Media Review

content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md

X — PASS

LinkedIn — PASS

Bluesky — PASS

Suggestions (advisory)

Uh oh!

djperlovsky commented Jul 29, 2026

Uh oh!

pulumi-bot commented Jul 29, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

cnunciato left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

cnunciato Jul 30, 2026

Choose a reason for hiding this comment

Uh oh!

djperlovsky Jul 30, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

github-actions Bot commented Jul 31, 2026

Pre-merge Review — Last updated 2026-07-31T21:19:35Z

🔍 Verification trail

📊 Editorial balance

🚨 Outstanding in this PR

⚠️ Low-confidence

Style findings

Uh oh!

github-actions Bot commented Jul 31, 2026

📋 Triaged verifier findings

💡 Pre-existing issues in touched files (optional)

✅ Resolved since last review

📜 Review history

Uh oh!

djperlovsky commented Jul 31, 2026

Uh oh!

github-actions Bot commented Jul 31, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

djperlovsky commented Jul 29, 2026 •

edited by cnunciato

Loading

github-actions Bot commented Jul 29, 2026 •

edited

Loading

pulumi-bot commented Jul 29, 2026 •

edited

Loading