Components: Packaging Components Guide #16795
Description
Create a guide that explains the packaging strategy options: single-language native packages (like npm), Pulumi Components, and a "heavy-duty" plugin with a schema (Pulumi Go Provider, basically).
Create a new page "Packaging a Component". Make it a sibling of the current "Build a Component" guide. The content should have the following basic structure:
- The process of authoring a component: inheriting from ComponentResource, etc. is identical between all approaches (with the exception that inputs and outputs for components distributed in a Pulumi package have some restrictions on what types they can support).
- Give a summary of the 3 packaging options and their pros/cons: single-language packages, local packages, "heavy-duty" plugins.
- Include https://www.pulumi.com/docs/iac/concepts/components/#adding-multi-language-support (and remove from its original source)
- Move content from https://www.pulumi.com/docs/iac/guides/building-extending/components/build-a-component/#sharing-and-reuse into this page.
- The section https://www.pulumi.com/docs/iac/guides/building-extending/components/build-a-component/#sharing-via-pulumi-package should be removed because it refers to publishing to the Pulumi (public) Registry.
Finally, we can include this detailed table at the end of the guide: https://www.pulumi.com/docs/iac/concepts/components/#the-spectrum-of-pulumi-components-you-can-build
We will need to expand the table to both clarify some of the existing items and add additional ones. (Exact list TBD.)
The following pages should have links to the packaging guide:
- Components (concepts page)
- Build a Component (from where we removed the content on packaging a component)
Related: #15396