Add blog post: Filling the Gaps in Terraform-to-Pulumi Migration - #21132
Draft
jdavredbeard wants to merge 7 commits into
Draft
Add blog post: Filling the Gaps in Terraform-to-Pulumi Migration#21132jdavredbeard wants to merge 7 commits into
jdavredbeard wants to merge 7 commits into
Conversation
Introduces pulumi-tool-import and its agent skills: the digest → resolve → import → patch-state pipeline for migrating Terraform (and CDK/CFN) workspaces onto the AWS Classic provider, with secrets handled via encrypted stack config, batched failure-isolating imports, state patching for fields the cloud API doesn't return, and state injection for non-importable resources. Adds author profile for jonathan-davenport. Date is a 2099-01-01 placeholder until a publish date is chosen. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
jdavredbeard
had a problem deploying
to
production
August 25, 2026 19:15 — with 
GitHub Actions
Error
GitHub Actions
Error
Publish date 2026-08-31; social copy for X/LinkedIn/Bluesky (passed critique review); clarify the tool is a ProServ-maintained Pulumi CLI tool plugin using the Automation API, not part of the core product. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
jdavredbeard
had a problem deploying
to
production
August 25, 2026 19:19 — with
GitHub Actions
Error
GitHub Actions
Error
Contributor
Social Media Reviewcontent/blog/filling-the-gaps-in-terraform-to-pulumi-migration/index.mdX — PASSLinkedIn — PASSBluesky — PASSUpdated for commit |
…ulty Reframe the intro and gaps section: migration is doable and the gaps are mechanical/automatable, with the 4,000-resource self-service customer as the proof point up front. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
jdavredbeard
temporarily deployed
to
production
August 25, 2026 19:23 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
Intro concedes migrations are hard but frames the gaps as mechanical and largely upstream of Pulumi (AWS write-only API design, Terraform providers shipping without importers), per the root-cause taxonomy in the tool repo's aws-import-diff-fields.md. Social copy recast so the customer's 4,000-resource migration reads as enabled by the tool, not endured despite the gaps. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
jdavredbeard
temporarily deployed
to
production
August 25, 2026 19:29 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
Collaborator
|
Your site preview for commit 01b6c2f is ready! 🎉 http://www-testing-pulumi-docs-origin-pr-21132-01b6c2f6.s3-website.us-west-2.amazonaws.com Changed pages: |
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
jdavredbeard
temporarily deployed
to
production
August 25, 2026 20:15 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
…digest The command requires --state-file and extracts explicitly mapped values from Terraform state via the same config-writing helpers as the digest's automatic pass — it is not for secrets outside state. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
jdavredbeard
temporarily deployed
to
production
August 25, 2026 20:27 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
The CFN front end is less built out; keep the post focused on the Terraform workflow. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
jdavredbeard
temporarily deployed
to
production
August 25, 2026 20:29 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
cnunciato
self-requested a review
August 27, 2026 05:27
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
New engineering blog post introducing
pulumi-tool-importand its agent skills for Terraform → Pulumi (AWS Classic) migration.digest → resolve → import → patch-state → zero-diff previewpipeline and the migration pain points each stage addresses: in-memory secret handling with encryption to stack config, reproducible import files via the mappings file, batched failure-isolating imports, state patching for fields the cloud API doesn't return, and state injection for non-importable resources.data/team/team/jonathan-davenport.toml./blog-feature-image(feature-logo-2: Terraform + Pulumi).Before ready-for-review
🤖 Generated with Claude Code