-
Notifications
You must be signed in to change notification settings - Fork 468
✨ Community Announcement ✨ #2386
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
This functionality has been released in Transfer of the Terraform Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
The development and maintenance of this provider has transitioned to VMware by Broadcom under the All previously released versions from ... this provider has moved to vmware/vsphere. Please update your source in required_providers. Tip Please be sure to update your configurations from |
Uh oh!
There was an error while loading. Please reload this page.
We're excited to share some news about the Terraform provider for VMware vSphere!
Important
The development and maintenance of this provider has transitioned to VMware by Broadcom under the
github.com/vmware
organization and thevmware
namespace on the Terraform Registry. 🥳 🎉2025-05-12
- v2.13.0 has been released under thevmware/vsphere
namespace on the Terraform Registry. The Terraform Registry team is in the progress of migratinghashicorp/vsphere
to this new location while retaining all versions, metrics, and adding a redirect notice.When using the Terraform CLI you will see this message:
v2.13.0 is now available on the Terraform Registry.
All previously released versions from
hashicorp/vsphere
now appear on the Terraform Registry undervmware/vsphere
.2025-05-05
- We are still in the process of getting all changes made with the team at HashiCorp to make the updates on the Terraform Registry.Myself and the the rest of the maintainers have established a valuable partnership with the team at HashiCorp, and we're incredibly grateful for their contributions and continued guidance. We want to assure the community that we are committed to ensuring a seamless transition and that the provider on the Terraform Registry will continue to function as expected, and we anticipate no required changes to your existing configurations.
Thistransition underscores VMware by Broadcom's dedication to the vSphere provider and the broader Terraform ecosystem. We are committed to:
Continuing development: We are eager to invest in the provider's future, bringing new features and improvements to better serve your needs.
Maintaining stability: We will continue to iterate to enhance the provider's stability and reliability for your infrastructure automation.
Fostering community engagement: We highly value your feedback and look forward to collaborating with you on the provider's evolution. We'll be opening the GitHub Discussions once the transfer has completed, too!
We're excited about this next step and the opportunity to further enhance the Terraform provider for VMware vSphere in collaboration with you.
Ryan Johnson
Distinguished Engineer, VMware by Broadcom
Tranfer Related Pull Requests:
The text was updated successfully, but these errors were encountered: