feat: add data source vgpu profiles

[mristok]

Description

Add a new data source to the provider to query and return available vGPU profiles for a host.

Acceptance tests

• Have you added an acceptance test for the functionality being added?
• Have you run the acceptance tests on this branch?

No acceptance tests added.

Provider tests

Output from provider testing:

ESXi host with A100 GPU

ESXi host with A100 GPU - no vGPU profile name filter

Changes to Outputs:
  + all_host_vgpu_profiles = {
      + host_id       = "host-1021"
      + id            = "fdcccc4252c0516e9d54a1ee6e851ba9f336c64502d6e80c5a684072f6e02bdc"
      + name          = null
      + vgpu_profiles = [
          + {
              + disk_snapshot_supported   = true
              + memory_snapshot_supported = true
              + migrate_supported         = true
              + suspend_supported         = true
              + vgpu                      = "grid_a100d-4c"
            },
          + {
              + disk_snapshot_supported   = true
              + memory_snapshot_supported = true
              + migrate_supported         = true
              + suspend_supported         = true
              + vgpu                      = "grid_a100d-8c"
            },
          + {
              + disk_snapshot_supported   = true
              + memory_snapshot_supported = true
              + migrate_supported         = true
              + suspend_supported         = true
              + vgpu                      = "grid_a100d-10c"
            },
          + {
              + disk_snapshot_supported   = true
              + memory_snapshot_supported = true
              + migrate_supported         = true
              + suspend_supported         = true
              + vgpu                      = "grid_a100d-16c"
            },
          + {
              + disk_snapshot_supported   = true
              + memory_snapshot_supported = true
              + migrate_supported         = true
              + suspend_supported         = true
              + vgpu                      = "grid_a100d-20c"
            },
          + {
              + disk_snapshot_supported   = true
              + memory_snapshot_supported = true
              + migrate_supported         = true
              + suspend_supported         = true
              + vgpu                      = "grid_a100d-40c"
            },
          + {
              + disk_snapshot_supported   = true
              + memory_snapshot_supported = true
              + migrate_supported         = true
              + suspend_supported         = true
              + vgpu                      = "grid_a100d-80c"
            },
        ]
    }

ESXi host with A100 GPU - vGPU profile name filter grid_a100d-80c

Changes to Outputs:
  + single_host_vgpu_profile = {
      + host_id       = "host-1021"
      + id            = "fdcccc4252c0516e9d54a1ee6e851ba9f336c64502d6e80c5a684072f6e02bdc"
      + name          = "grid_a100d-80c"
      + vgpu_profiles = [
          + {
              + disk_snapshot_supported   = true
              + memory_snapshot_supported = true
              + migrate_supported         = true
              + suspend_supported         = true
              + vgpu                      = "grid_a100d-80c"
            },
        ]
    }

ESXi host without GPU

ESXi host without GPU - no vGPU profile name filter

Changes to Outputs:
  + all_host_vgpu_profiles = {
      + host_id       = "host-4016"
      + id            = "7025a70fb666db1fd6f2f0d3f27ca9c6cb574a780443fd37d49685275e5b9b66"
      + name          = null
      + vgpu_profiles = []
    }

ESXi host without GPU - vGPU profile name filter grid_a100d-80c

Changes to Outputs:
  + single_host_vgpu_profiles = {
      + host_id       = "host-4016"
      + id            = "7025a70fb666db1fd6f2f0d3f27ca9c6cb574a780443fd37d49685275e5b9b66"
      + name          = "grid_a100d-80c"
      + vgpu_profiles = []
    }

Release Note

Release note for CHANGELOG:

...

References

Closes #2047

[hashicorp-cla]

All committers have signed the CLA.

[tenthirtyam]

The markdown for the data source docs should also be included.

[vasilsatanasov]

Hi @mristok this is a great augmentation to the provider but I think that this data should be part of the vsphere_host data source. This will make it more consistent for the users as they will have to write less HCL code. I also do not see an acceptance test for this functionality and this will be a very good addition to the PR.

Best regards, Vasil

[mristok]

@vasilsatanasov This functionality can be moved into the vsphere_host data source; the reason I made it separate was so that it was aligned with the vsphere_host_pci_device being a separate data source.

Also, I did not add any acceptance tests to this given that the GPU based hardware in Equinix Metal is expensive (and based on 12/36 month contracts). If this were to be added to the acceptance tests would the following be in line with your vision:

• User must specify a GPU ESXi host (not part of the standard acceptance test deployment)
  • Example: TF_VAR_VSPHERE_TEST_GPU_ESXI
• If no GPU ESXi host is specified, the test is skipped

[vasilsatanasov]

LGTM!

[tenthirtyam]

lgtm

[github-actions]

This functionality has been released in v2.7.0 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!

[github-actions]

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.