Expanding the Pulumi Registry: 27 New Providers to Expand the Ecosystem #14402
+74
−0
Conversation
This file contains 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
|
Your site preview for commit 59b36e7 is ready! 🎉 http://www-testing-pulumi-docs-origin-pr-14402-59b36e76.s3-website.us-west-2.amazonaws.com. |
mjeffryes
approved these changes
Mar 15, 2025
|
|
||
| <!--more--> | ||
|
|
||
| This milestone is made possible by Pulumi's new capability to support [any Terraform provider](https://www.pulumi.com/registry/packages/terraform-provider/) (bridging existing Terraform providers for use in Pulumi), as detailed in our [recent blog post about Any Terraform Provider support](/blog/any-terraform-provider/). With this capability, Pulumi users can now leverage an even broader range of infrastructure and SaaS providers, all within the familiar Pulumi programming model. To ensure the best developer experience, we've also added comprehensive documentation for these new providers directly in the [Pulumi Registry](https://www.pulumi.com/registry/). This means you can find everything you need right where you're already spending time. |
There was a problem hiding this comment.
Suggested change
| This milestone is made possible by Pulumi's new capability to support [any Terraform provider](https://www.pulumi.com/registry/packages/terraform-provider/) (bridging existing Terraform providers for use in Pulumi), as detailed in our [recent blog post about Any Terraform Provider support](/blog/any-terraform-provider/). With this capability, Pulumi users can now leverage an even broader range of infrastructure and SaaS providers, all within the familiar Pulumi programming model. To ensure the best developer experience, we've also added comprehensive documentation for these new providers directly in the [Pulumi Registry](https://www.pulumi.com/registry/). This means you can find everything you need right where you're already spending time. | |
| This milestone is made possible by Pulumi's new ability to use [any Terraform provider](https://www.pulumi.com/registry/packages/terraform-provider/) (bridging existing Terraform providers for use in Pulumi), as detailed in our [recent blog post](/blog/any-terraform-provider/). Since that announcement, Pulumi users have already begun to use many of the new infrastructure and SaaS providers that are now accessible within the familiar Pulumi programming model. To ensure the best developer experience, we've also added comprehensive documentation for 27 of these new providers directly in the [Pulumi Registry](https://www.pulumi.com/registry/). This means you can find everything you need right where you're already spending time. |
A few nits:
- "ability to use" seems more fluid to me than "capability to support"
- link test to the blog seemed redundant with the sentence
- specifying the number of providers receiving new docs may help clarify that the limited list of documented providers does not limit which TF providers that can be used this way.
I also made a bigger tweak to the transition sentence, again trying to make it clear that the docs were adding are just an enhancement for a subset of TF providers not a limit to what providers you can use.
Weak opinions on all of these changes though.
|
|
||
| This release represents just the first wave of our expanded provider documentation initiative. We've prioritized these initial 27 providers based on direct user and customer feedback. We're committed to continuing this effort, with plans to add documentation for many more providers to the Pulumi Registry in the coming months. Our goal is to create the most comprehensive and user-friendly infrastructure as code ecosystem, making it even easier for you to manage your entire cloud infrastructure from a single platform. | ||
|
|
||
| This update is designed with developers in mind and features enriched documentation directly in the Registry, ensuring you have all the resources you need right at your fingertips. We're also spotlighting a few providers providers: |
There was a problem hiding this comment.
Suggested change
| This update is designed with developers in mind and features enriched documentation directly in the Registry, ensuring you have all the resources you need right at your fingertips. We're also spotlighting a few providers providers: | |
| This update is designed with developers in mind and features enriched documentation directly in the Registry, ensuring you have all the resources you need right at your fingertips. We're also spotlighting a few partner providers: |
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
Proposed changes
Unreleased product version (optional)
Related issues (optional)