Add blog post for ESC terraform-state provider

[nyobe]

Proposed changes

Draft announcement blog post for the terraform-state ESC provider, which reads outputs from Terraform state files (S3 or Terraform Cloud) into ESC environments, which, while documented (#16419), was never announced.

Related issues

• Closes: https://github.com/pulumi/pulumi-service/issues/37094

[claude]

Documentation Review

This blog post announcing the terraform-state provider for Pulumi ESC is well-written with good structure and clear examples. However, there are several issues that need to be addressed before publishing:

Critical Issues

1. Missing Documentation (BLOCKER)

The blog post references documentation at /docs/esc/integrations/infrastructure/terraform/terraform-state/ multiple times (lines 15 and 71), but this documentation does not exist in the repository.

Since this blog post announces a new feature, the corresponding documentation must be created and published before or alongside this blog post. The blog should not link to non-existent documentation.

Required action: Create comprehensive documentation for the terraform-state provider at the referenced location, including:

• Complete API reference for the provider
• Configuration options for both S3 and Terraform Cloud backends
• Examples covering common use cases
• Security best practices
• Troubleshooting guidance

2. Meta Image Verification Required

The PR description explicitly notes: "TODO: Replace placeholder meta image before publish"

While I cannot visually verify whether the current meta.png (28K, 1200x600) is a placeholder or the final image, this TODO in the PR description indicates it needs review. According to the review criteria, we must ensure the meta image is not a default placeholder.

Required action: Confirm the meta.png has been replaced with a final, relevant image for this blog post before publishing.

Style and Content Issues

3. Missing alt text for meta image

While the meta.png is referenced in frontmatter, there's no alt text specified. The image should include descriptive alt text for accessibility.

4. Minor style feedback

The content is clear and well-structured. The examples are realistic and show practical use cases. The writing follows the blog post guidelines with:

• ✓ Clear, engaging title
• ✓ Strong opening that establishes the problem
• ✓ Good structure with headings
• ✓ Concise paragraphs
• ✓ Clear call-to-action at the end
• ✓ No AI-generated filler or vague generalities

Summary

This blog post is well-written and ready for publication once the blocking issues are resolved:

1. Create the missing terraform-state provider documentation
2. Confirm/replace the meta image placeholder
3. Add alt text for the meta image

The author information (claire-gaestel) is properly configured in data/team/team/claire-gaestel.toml.

---

@Claire mention @claude if you'd like additional reviews or help addressing these issues.

[pulumi-bot]

Your site preview for commit 573c01f is ready! 🎉

http://www-testing-pulumi-docs-origin-pr-17542-573c01fa.s3-website.us-west-2.amazonaws.com.

[pulumi-bot]

Your site preview for commit 04c9ed7 is ready! 🎉

http://www-testing-pulumi-docs-origin-pr-17542-04c9ed70.s3-website.us-west-2.amazonaws.com.

[pgavlin]

Two small grammar / style nits, but LGTM otherwise.

[pulumi-bot]

Your site preview for commit f1577c2 is ready! 🎉

http://www-testing-pulumi-docs-origin-pr-17542-f1577c2e.s3-website.us-west-2.amazonaws.com.