Skip to content

✨ 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

Closed
18 tasks done
tenthirtyam opened this issue Apr 22, 2025 · 2 comments
Closed
18 tasks done

✨ Community Announcement ✨ #2386

tenthirtyam opened this issue Apr 22, 2025 · 2 comments
Assignees
Labels
announcement Announcement
Milestone

Comments

@tenthirtyam
Copy link
Contributor

tenthirtyam commented Apr 22, 2025

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 the vmware namespace on the Terraform Registry. 🥳 🎉

  • 2025-05-12 - v2.13.0 has been released under the vmware/vsphere namespace on the Terraform Registry. The Terraform Registry team is in the progress of migrating hashicorp/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:

    ... this provider has moved to vmware/vsphere. Please update your source in required_providers.

    v2.13.0 is now available on the Terraform Registry.

    All previously released versions from hashicorp/vsphere now appear on the Terraform Registry under vmware/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:

@tenthirtyam tenthirtyam added enhancement Enhancement and removed enhancement Enhancement labels Apr 22, 2025
@tenthirtyam tenthirtyam self-assigned this Apr 22, 2025
@tenthirtyam tenthirtyam added this to the On Deck milestone Apr 22, 2025
@tenthirtyam tenthirtyam changed the title Placeholder ✨ Community Announcement ✨ Apr 22, 2025
@tenthirtyam tenthirtyam pinned this issue Apr 22, 2025
@tenthirtyam tenthirtyam added the announcement Announcement label Apr 22, 2025
@tenthirtyam tenthirtyam removed this from the On Deck milestone Apr 26, 2025
@tenthirtyam tenthirtyam added this to the Transfer milestone May 5, 2025
@tenthirtyam tenthirtyam assigned spacegospod and dougm and unassigned dougm May 6, 2025
Copy link

github-actions bot commented May 6, 2025

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!

@vmware vmware locked and limited conversation to collaborators May 7, 2025
@tenthirtyam tenthirtyam unpinned this issue May 12, 2025
@tenthirtyam tenthirtyam pinned this issue May 12, 2025
@tenthirtyam tenthirtyam unpinned this issue May 13, 2025
@tenthirtyam tenthirtyam pinned this issue May 13, 2025
@tenthirtyam
Copy link
Contributor Author

The development and maintenance of this provider has transitioned to VMware by Broadcom under the github.com/vmware organization and the vmware/vsphere namespace on the Terraform Registry. 🥳 🎉

All previously released versions from hashicorp/vsphere have been resigned and now appear on the Terraform Registry under vmware/vsphere. You will begin to see the following in the Terraform CLI when using the provider:

... this provider has moved to vmware/vsphere. Please update your source in required_providers.

Tip

Please be sure to update your configurations from hashicorp/vsphere to vmware/vsphere.

@tenthirtyam tenthirtyam unpinned this issue May 17, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
announcement Announcement
Projects
None yet
Development

No branches or pull requests

3 participants