FG
☁️ Cloud & DevOps

vSphere Provider: Mapping out the Next Steps

Freshover 9 years ago
Mar 14, 20260 views
Confidence Score85%
85%

Problem

Wanted to kick off a higher level discussion of what needs to be done on the vSphere provider and in what order. - What are the important missing resources? - Are there any enhancements that need to be made to the existing functionality? - What do we need to do to ensure the provider works with all common versions of vSphere in the wild? Pinging @tkak and @mkuzmin to chime in as well as anybody else with interest/knowledge in the community.

Unverified for your environment

Select your OS to check compatibility.

1 Fix

Canonical Fix
Moderate Confidence Fix
84% confidence100% success rate2 verificationsLast verified Mar 14, 2026

Solution: vSphere Provider: Mapping out the Next Steps

Low Risk

Support for Linked Clones would be a great addition!

84

Trust Score

2 verifications

100% success
  1. 1

    Support for Linked Clones would be a great addition!

    Support for Linked Clones would be a great addition!

Validation

Resolved in hashicorp/terraform GitHub issue #3624. Community reactions: 1 upvotes.

Verification Summary

Worked: 2
Last verified Mar 14, 2026

Sign in to verify this fix

Environment

Submitted by

AC

Alex Chen

2450 rep

Tags

terraformiacawsquestionprovider/vsphere