Skip to content

Conversation

@jkodroff
Copy link
Member

Fixes #16367

Improved the introduction to better explain the different types of Pulumi Packages that can be published (components, custom providers, and bridged providers). Added distinction between public packages and organizational components, directing users to the appropriate guide based on their needs. Also fixed spelling (customisation → customization) and improved formatting for better readability.

🤖 Generated with Claude Code

@claude
Copy link
Contributor

claude bot commented Oct 24, 2025

Review Summary

Thank you for improving the introduction to better clarify the different types of Pulumi Packages and their publishing scope. The changes help users understand when to use this guide versus the organizational components guide.

Issues Found

Critical Issues

Line 28 - Typo in CRUD acronym
CRUB operations should be CRUD operations (Create, Read, Update, Delete)

- A bridged provider, which wraps an existing Terraform provider and leverages its code to perform the CRUD operations for each resource type

Line 24 - Broken link
The link /docs/iac/concepts/packages does not resolve to an existing page. Based on the Hugo aliases configuration, this should link to /docs/iac/guides/building-extending/packages/

This guide will take you through the process to create and publish a [Pulumi Package](/docs/iac/guides/building-extending/packages/) to the [Pulumi Registry](/registry). You can use this guide to publish the following types of Pulumi Packages:

Minor Issues

Line 31 - Grammar
Extra article "a" before "looking"

This guide is for creating packages for public consumption. If you are looking for information on how to create and publish components for use within your organization, see [Build a Component](/docs/iac/guides/building-extending/components/build-a-component).

Positive Changes

  • Excellent clarification between public packages and organizational components
  • Good addition of the distinction between component, custom provider, and bridged provider types
  • Improved structure with the moved GitHub assumptions note
  • Correct spelling fix (customisation → customization)

Mention @claude if you'd like me to review additional changes or help fix these issues.

@pulumi-bot
Copy link
Collaborator

Improved the introduction to better explain the different types of Pulumi
Packages that can be published (components, custom providers, and bridged
providers). Added distinction between public packages and organizational
components, directing users to the appropriate guide based on their needs.
Also fixed spelling (customisation → customization) and improved formatting
for better readability.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
@jkodroff jkodroff force-pushed the jkodroff/publishing-packages-clarification branch from 4fae39c to 2bd95ba Compare October 24, 2025 15:56
@pulumi-bot
Copy link
Collaborator

Copy link
Contributor

@CamSoper CamSoper left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great, thanks for doing this!

@jkodroff jkodroff merged commit 5de4edd into master Oct 24, 2025
11 checks passed
@jkodroff jkodroff deleted the jkodroff/publishing-packages-clarification branch October 24, 2025 17:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Publishing Packages: Make it clear that this guide is specifically for publishing on the Pulumi Registry

3 participants