Add blog post on PostgreSQL state backend support for Pulumi #15271
Conversation
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
This commit introduces a new blog post detailing the community-driven journey to add PostgreSQL as a state backend option for Pulumi's DIY backend. The post covers the need for database-backed state storage, the community contribution process, technical challenges faced during implementation, and future possibilities for enhancements. Additionally, it includes a new author profile for Matan Baruch and associated images for the blog post.
Frassle
reviewed
Jun 10, 2025
Failure looks weird. |
adamgordonbell
requested changes
Jun 11, 2025
Co-authored-by: Adam Gordon Bell <[email protected]>
|
@adamgordonbell Is there anything blocking this? |
Hey @matanbaruch, apologies as i was away for several days. But i have some updated wording on the 'limitations' part I would like to run by you in a coming PR I'll create and then we are good. |
- Remove Implementation Deep Dive and Testing Quality Assurance sections to streamline content - Add PostgreSQL vs S3 comparison highlighting ACID transactions, performance, backups, observability - Add Pulumi Cloud feature gaps section covering CrossGuard, drift detection, deployments, RBAC - Update all list formatting from dashes to asterisks for consistency - Add bold formatting to section headers for better visual hierarchy - Update intro to emphasize DIY approach preference over managed solution - Simplify conclusion to focus on improved DIY state management approach
- Update all bullet points throughout the document to use dashes instead of asterisks for consistency with standard markdown formatting
- Change intro to highlight Pulumi Cloud as fully managed, secure, and scalable - Position DIY PostgreSQL backend as option for teams who choose self-hosting - Add caveat about operational overhead and considerations needed for DIY approach
|
@matanbaruch suggested rewording from product team at Pulumi here: matanbaruch#1 |
Merged |
adamgordonbell
approved these changes
Jun 16, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This pull request introduces a new blog post detailing the addition of PostgreSQL as a state backend for Pulumi's DIY backend, along with a new author profile for the contributor of this feature. The blog post outlines the technical implementation, community-driven development process, and future possibilities for the feature.
Blog Post Addition:
content/blog/postgres-diy-backend/index.md: Added a comprehensive blog post titled "Adding PostgreSQL State Backend Support to Pulumi: A Community Contribution Journey." The post covers the motivation, technical challenges, implementation details, testing, and community impact of the new PostgreSQL state backend feature.Author Profile:
data/team/team/matan-baruch.toml: Added a new author profile for Matan Baruch, the community contributor behind the PostgreSQL backend feature. Includes social media links and contributor status.