Add accelerator_topology_mode to google_compute_resource_policy#16641
Conversation
|
Googlers: For automatic test runs see go/terraform-auto-test-runs. @hao-nan-li, a repository maintainer, has been assigned to review your changes. If you have not received review feedback within 2 business days, please leave a comment on this PR asking them to take a look. You can help make sure that review is quick by doing a self-review and by running impacted tests locally. |
|
Hi there, I'm the Modular magician. I've detected the following information about your changes: Diff reportYour PR generated some diffs in downstreams - here they are.
|
Tests analyticsTotal tests: 1382 Click here to see the affected service packages
Action takenFound 2 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests
|
|
@hao-nan-li sending a follow-up PR, because I noticed I incorrectly affected the GA provider, but the change should affect only the |
Description
This PR adds support for the
accelerator_topology_modefield in thegoogle_compute_resource_policyresource, specifically within theworkload_policyblock.This enables "Super-slicing" for TPU clusters on GKE by allowing users to set the topology mode to values such as
PROVISION_ONLYorAUTO_CONNECT. The field aligns with the underlying Compute Engine API andgcloud beta compute resource-policies create workload-policy --accelerator-topology-modecapabilities.Changes Made:
acceleratorTopologyModetommv1/products/compute/ResourcePolicy.yamlas anEnumtype.accelerator_topology_mode,accelerator_topology, andmax_topology_distance.resource_policy_workload_policy_accelerator_topology_mode) to auto-generate documentation.TestAccComputeResourcePolicy_withTopologyMode) to verify creation and destruction.Release Note Template for Downstream PRs (will be copied)