Blog: Importing a GCP Project into Pulumi with Neo

[kramhuber]

No description provided.

[kramhuber]

@claude do another review

[pulumi-bot]

Your site preview for commit 354e53b is ready! 🎉

http://www-testing-pulumi-docs-origin-pr-18617-354e53bf.s3-website.us-west-2.amazonaws.com

[kramhuber]

Social Media Review

content/blog/importing-a-gcp-project-with-neo/index.md

X — FAIL

Reasons:

• Missing pointer: "review the pull request" reads as an instruction to the reader, not a signal the article has more detail
• Reads like a product announcement: "Now, just hand the project to Neo, and review the pull request" is release-note language

LinkedIn — FAIL

Reasons:

• Missing pointer: same issue — ends with a feature description rather than a clear signal to read more
• Reads like a product announcement: same closing line as X

Bluesky — FAIL

Reasons:

• Identical to X copy despite Bluesky allowing 300 chars vs. X's 255
• Missing pointer: same issue as X

Suggested copy

X (219/255 chars):

A typical GCP project import meant identifying every resource type and ID by hand, then running pulumi import one by one. For a busy project, that was days.
We described the scope to Neo instead. Here's what came back.

LinkedIn (306/2950 chars):

A production GCP project doesn't stay small. A VPC, compute instances, a database, a handful of storage buckets — after a year of Console clicks, listing every resource type and ID by hand just to run pulumi import could take days.
That's the project we handed to Neo.
Here's what the import looked like.

Bluesky (217/300 chars):

A GCP project with a VPC, two instances, a database, and storage buckets is days of manual import work. Listing resource types and IDs alone takes hours.
We handed it to Neo. Here's what the pull request looked like.

To apply these suggestions, comment: @claude please update the social posts in the frontmatter with the suggested copy from the social media review above

To re-run the social media review after updates, comment: /social-review

I'm not using these

[github-actions]

Social Media Review

content/blog/importing-a-gcp-project-with-neo/index.md

X — PASS

• 231/255 chars
• Two paragraphs, no banned phrases, no hashtags

LinkedIn — PASS

• 437/2950 chars
• Multiple short paragraphs; "was days of work" grounds the pain point concretely

Bluesky — PASS

• 206/300 chars
• Identical structure to X, within limits

---

To apply these suggestions, comment: @claude please update the social posts in the frontmatter with the suggested copy from the social media review above

To re-run the social media review after updates, comment: /social-review