Skip to content

Add autoscaling settings to pc management cluster #12002

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

Merged
merged 14 commits into from
Oct 28, 2024

Conversation

varshatumburu
Copy link
Contributor

@varshatumburu varshatumburu commented Oct 15, 2024

Add terraform support for autoscaling in pc management cluster

Private Cloud Acceptance Tests pass at gpaste/5685698748481536

Release Note Template for Downstream PRs (will be copied)

vmwareengine: added `autoscaling_settings` to `google_vmwareengine_private_cloud` resource

@modular-magician
Copy link
Collaborator

Hi there, I'm the Modular magician. I've detected the following information about your changes:

Diff report

Your PR generated some diffs in downstreams - here they are.

google provider: Diff ( 3 files changed, 1017 insertions(+), 5 deletions(-))
google-beta provider: Diff ( 3 files changed, 1017 insertions(+), 5 deletions(-))
terraform-google-conversion: Diff ( 1 file changed, 285 insertions(+))

Missing test report

Your PR includes resource fields which are not covered by any test.

Resource: google_vmwareengine_private_cloud (13 total tests)
Please add an acceptance test which includes these fields. The test should include the following:

resource "google_vmwareengine_private_cloud" "primary" {
  management_cluster {
    autoscaling_settings {
      autoscaling_policies {
        consumed_memory_thresholds {
          scale_in  = # value needed
          scale_out = # value needed
        }
        granted_memory_thresholds {
          scale_in  = # value needed
          scale_out = # value needed
        }
      }
    }
  }
}

@modular-magician
Copy link
Collaborator

Tests analytics

Total tests: 14
Passed tests: 12
Skipped tests: 2
Affected tests: 0

Click here to see the affected service packages
  • vmwareengine

🟢 All tests passed!

View the build log

@modular-magician
Copy link
Collaborator

Hi there, I'm the Modular magician. I've detected the following information about your changes:

Diff report

Your PR generated some diffs in downstreams - here they are.

google provider: Diff ( 3 files changed, 1017 insertions(+), 5 deletions(-))
google-beta provider: Diff ( 3 files changed, 1017 insertions(+), 5 deletions(-))
terraform-google-conversion: Diff ( 1 file changed, 285 insertions(+))

Missing test report

Your PR includes resource fields which are not covered by any test.

Resource: google_vmwareengine_private_cloud (13 total tests)
Please add an acceptance test which includes these fields. The test should include the following:

resource "google_vmwareengine_private_cloud" "primary" {
  management_cluster {
    autoscaling_settings {
      autoscaling_policies {
        consumed_memory_thresholds {
          scale_in  = # value needed
          scale_out = # value needed
        }
        granted_memory_thresholds {
          scale_in  = # value needed
          scale_out = # value needed
        }
      }
    }
  }
}

@modular-magician
Copy link
Collaborator

Tests analytics

Total tests: 14
Passed tests: 12
Skipped tests: 2
Affected tests: 0

Click here to see the affected service packages
  • vmwareengine

🟢 All tests passed!

View the build log

@modular-magician
Copy link
Collaborator

Hi there, I'm the Modular magician. I've detected the following information about your changes:

Diff report

Your PR generated some diffs in downstreams - here they are.

google provider: Diff ( 3 files changed, 1029 insertions(+), 5 deletions(-))
google-beta provider: Diff ( 3 files changed, 1029 insertions(+), 5 deletions(-))
terraform-google-conversion: Diff ( 1 file changed, 285 insertions(+))

@varshatumburu varshatumburu changed the title Add autoscale settings to pc management cluster Add autoscaling settings to pc management cluster Oct 15, 2024
@modular-magician
Copy link
Collaborator

Tests analytics

Total tests: 14
Passed tests: 12
Skipped tests: 2
Affected tests: 0

Click here to see the affected service packages
  • vmwareengine

🟢 All tests passed!

View the build log

@modular-magician
Copy link
Collaborator

Hi there, I'm the Modular magician. I've detected the following information about your changes:

Diff report

Your PR generated some diffs in downstreams - here they are.

google provider: Diff ( 3 files changed, 1029 insertions(+), 5 deletions(-))
google-beta provider: Diff ( 3 files changed, 1029 insertions(+), 5 deletions(-))
terraform-google-conversion: Diff ( 1 file changed, 285 insertions(+))

1 similar comment
@modular-magician
Copy link
Collaborator

Hi there, I'm the Modular magician. I've detected the following information about your changes:

Diff report

Your PR generated some diffs in downstreams - here they are.

google provider: Diff ( 3 files changed, 1029 insertions(+), 5 deletions(-))
google-beta provider: Diff ( 3 files changed, 1029 insertions(+), 5 deletions(-))
terraform-google-conversion: Diff ( 1 file changed, 285 insertions(+))

@modular-magician
Copy link
Collaborator

Tests analytics

Total tests: 14
Passed tests: 12
Skipped tests: 2
Affected tests: 0

Click here to see the affected service packages
  • vmwareengine

🟢 All tests passed!

View the build log

@modular-magician
Copy link
Collaborator

Tests analytics

Total tests: 14
Passed tests: 12
Skipped tests: 2
Affected tests: 0

Click here to see the affected service packages
  • vmwareengine

🟢 All tests passed!

View the build log

@varshatumburu varshatumburu marked this pull request as ready for review October 16, 2024 09:06
@github-actions github-actions bot requested a review from zli82016 October 16, 2024 09:07
Copy link

Hello! I am a robot. Tests will require approval from a repository maintainer to run.

@zli82016, 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.

@modular-magician
Copy link
Collaborator

Hi there, I'm the Modular magician. I've detected the following information about your changes:

Diff report

Your PR generated some diffs in downstreams - here they are.

google provider: Diff ( 3 files changed, 811 insertions(+), 5 deletions(-))
google-beta provider: Diff ( 3 files changed, 811 insertions(+), 5 deletions(-))
terraform-google-conversion: Diff ( 1 file changed, 222 insertions(+))

@modular-magician
Copy link
Collaborator

Tests analytics

Total tests: 14
Passed tests: 12
Skipped tests: 2
Affected tests: 0

Click here to see the affected service packages
  • vmwareengine

🟢 All tests passed!

View the build log

@varshatumburu varshatumburu marked this pull request as draft October 16, 2024 11:09
@varshatumburu varshatumburu marked this pull request as ready for review October 16, 2024 17:39
@github-actions github-actions bot requested a review from zli82016 October 18, 2024 06:47
@modular-magician
Copy link
Collaborator

Hi there, I'm the Modular magician. I've detected the following information about your changes:

Diff report

Your PR generated some diffs in downstreams - here they are.

google provider: Diff ( 3 files changed, 811 insertions(+), 5 deletions(-))
google-beta provider: Diff ( 3 files changed, 811 insertions(+), 5 deletions(-))
terraform-google-conversion: Diff ( 1 file changed, 222 insertions(+))

@modular-magician
Copy link
Collaborator

Tests analytics

Total tests: 14
Passed tests: 12
Skipped tests: 2
Affected tests: 0

Click here to see the affected service packages
  • vmwareengine

🟢 All tests passed!

View the build log

@modular-magician
Copy link
Collaborator

Hi there, I'm the Modular magician. I've detected the following information about your changes:

Diff report

Your PR generated some diffs in downstreams - here they are.

google provider: Diff ( 3 files changed, 809 insertions(+), 5 deletions(-))
google-beta provider: Diff ( 3 files changed, 809 insertions(+), 5 deletions(-))
terraform-google-conversion: Diff ( 1 file changed, 222 insertions(+))

@modular-magician
Copy link
Collaborator

Tests analytics

Total tests: 14
Passed tests: 12
Skipped tests: 2
Affected tests: 0

Click here to see the affected service packages
  • vmwareengine

🟢 All tests passed!

View the build log

@zli82016
Copy link
Member

zli82016 commented Oct 21, 2024

Hello, @varshatumburu , I tried to create a resource with autoscaling_setttings in the configuration locally, but the test failed. It seems like the response doesn't have autoscaling_setttings.

GET /v1/projects/ci-test-project-188019/locations/me-west1-b/privateClouds/tf-test-sample-pcer48vrygfc/clusters?alt=json&filter=management%3Dtrue HTTP/1.1

-----------------------------------------------------
2024/10/19 00:18:47 [DEBUG] Google API Response Details:
---[ RESPONSE ]--------------------------------------

{
  "clusters": [
    {
      "name": "projects/ci-test-project-188019/locations/me-west1-b/privateClouds/tf-test-sample-pcer48vrygfc/clusters/tf-test-sample-mgmt-cluster-custom-core-counter48vrygfc",
      "createTime": "2024-10-19T00:12:58.449044150Z",
      "updateTime": "2024-10-19T00:12:59.228101035Z",
      "state": "ACTIVE",
      "management": true,
      "uid": "8504808a-cfc4-4b60-a0dc-de5fb27ee03d",
      "nodeTypeConfigs": {
        "standard-72": {
          "nodeCount": 3,
          "customCoreCount": 32
        }
      }
    }
  ]
}

Do you have an idea for the reason? Thanks.

@varshatumburu
Copy link
Contributor Author

Hello, @varshatumburu , I tried to create a resource with autoscaling_setttings in the configuration locally, but the test failed. It seems like the response doesn't have autoscaling_setttings.

GET /v1/projects/ci-test-project-188019/locations/me-west1-b/privateClouds/tf-test-sample-pcer48vrygfc/clusters?alt=json&filter=management%3Dtrue HTTP/1.1

-----------------------------------------------------
2024/10/19 00:18:47 [DEBUG] Google API Response Details:
---[ RESPONSE ]--------------------------------------

{
  "clusters": [
    {
      "name": "projects/ci-test-project-188019/locations/me-west1-b/privateClouds/tf-test-sample-pcer48vrygfc/clusters/tf-test-sample-mgmt-cluster-custom-core-counter48vrygfc",
      "createTime": "2024-10-19T00:12:58.449044150Z",
      "updateTime": "2024-10-19T00:12:59.228101035Z",
      "state": "ACTIVE",
      "management": true,
      "uid": "8504808a-cfc4-4b60-a0dc-de5fb27ee03d",
      "nodeTypeConfigs": {
        "standard-72": {
          "nodeCount": 3,
          "customCoreCount": 32
        }
      }
    }
  ]
}

Do you have an idea for the reason? Thanks.

Hi @zli82016, I would require more information and logs before and after to check. Could you also share the request that was made to update the cluster settings, and if there were any failure messages before/after?

@zli82016
Copy link
Member

zli82016 commented Oct 21, 2024

Hello, @varshatumburu , I didn't update the resource. Instead, I created the resource.

This is the request:

POST /v1/projects/ci-test-project-188019/locations/me-west1-b/privateClouds?alt=json&privateCloudId=tf-test-sample-pcer48vrygfc HTTP/1.1
Host: vmwareengine.googleapis.com
User-Agent: Terraform/1.8.3 (+https://www.terraform.io) Terraform-Plugin-SDK/2.33.0 terraform-provider-google-

{
 "description": "sample updated description",
 "managementCluster": {
  "autoscalingSettings": {
   "autoscalingPolicies": {
    "autoscaling-policy": {
     "consumedMemoryThresholds": {
      "scaleIn": 20,
      "scaleOut": 75
     },
     "cpuThresholds": {
      "scaleIn": 15,
      "scaleOut": 80
     },
     "nodeTypeId": "standard-72",
     "scaleOutSize": 1,
     "storageThresholds": {
      "scaleIn": 20,
      "scaleOut": 80
     }
    }
   },
   "maxClusterNodeCount": 8,
   "minClusterNodeCount": 3
  },
  "clusterId": "tf-test-sample-mgmt-cluster-custom-core-counter48vrygfc",
  "nodeTypeConfigs": {
   "standard-72": {
    "customCoreCount": 32,
    "nodeCount": 3
   }
  }
 },
 "networkConfig": {
  "managementCidr": "192.168.0.0/24",
  "vmwareEngineNetwork": "projects/ci-test-project-188019/locations/global/vmwareEngineNetworks/tf-test-pc-nw-er48vrygfc"
 }
}

The error I got for my test is that

error=
  | After applying this test step, the plan was not empty.
  | stdout:
  | 
  | 
  | Terraform used the selected providers to generate the following execution
  | plan. Resource actions are indicated with the following symbols:
  |   ~ update in-place
  |  <= read (data resources)
  | 
  | Terraform will perform the following actions:
  | 
  |   # data.google_vmwareengine_nsx_credentials.nsx-ds will be read during apply
  |   # (depends on a resource or a module with changes pending)
  |  <= data "google_vmwareengine_nsx_credentials" "nsx-ds" {
  |       + id       = (known after apply)
  |       + parent   = "projects/ci-test-project-188019/locations/me-west1-b/privateClouds/tf-test-sample-pcer48vrygfc"
  |       + password = (known after apply)
  |       + username = (known after apply)
  |     }
  | 
  |   # data.google_vmwareengine_private_cloud.ds will be read during apply
  |   # (depends on a resource or a module with changes pending)
  |  <= data "google_vmwareengine_private_cloud" "ds" {
  |       + deletion_delay_hours              = (known after apply)
  |       + description                       = (known after apply)
  |       + hcx                               = (known after apply)
  |       + id                                = (known after apply)
  |       + location                          = "me-west1-b"
  |       + management_cluster                = (known after apply)
  |       + name                              = "tf-test-sample-pcer48vrygfc"
  |       + network_config                    = (known after apply)
  |       + nsx                               = (known after apply)
  |       + send_deletion_delay_hours_if_zero = (known after apply)
  |       + state                             = (known after apply)
  |       + type                              = (known after apply)
  |       + uid                               = (known after apply)
  |       + vcenter                           = (known after apply)
  |     }
  | 
  |   # data.google_vmwareengine_vcenter_credentials.vcenter-ds will be read during apply
  |   # (depends on a resource or a module with changes pending)
  |  <= data "google_vmwareengine_vcenter_credentials" "vcenter-ds" {
  |       + id       = (known after apply)
  |       + parent   = "projects/ci-test-project-188019/locations/me-west1-b/privateClouds/tf-test-sample-pcer48vrygfc"
  |       + password = (known after apply)
  |       + username = (known after apply)
  |     }
  | 
  |   # google_vmwareengine_private_cloud.vmw-engine-pc will be updated in-place
  |   ~ resource "google_vmwareengine_private_cloud" "vmw-engine-pc" {
  |         id                                = "projects/ci-test-project-188019/locations/me-west1-b/privateClouds/tf-test-sample-pcer48vrygfc"
  |         name                              = "tf-test-sample-pcer48vrygfc"
  |         # (10 unchanged attributes hidden)
  | 
  |       ~ management_cluster {
  |             # (1 unchanged attribute hidden)
  | 
  |           + autoscaling_settings {
  |               + max_cluster_node_count = 8
  |               + min_cluster_node_count = 3
  | 
  |               + autoscaling_policies {
  |                   + autoscale_policy_id = "autoscaling-policy"
  |                   + node_type_id        = "standard-72"
  |                   + scale_out_size      = 1
  | 
  |                   + consumed_memory_thresholds {
  |                       + scale_in  = 20
  |                       + scale_out = 75
  |                     }
  | 
  |                   + cpu_thresholds {
  |                       + scale_in  = 15
  |                       + scale_out = 80
  |                     }
  | 
  |                   + storage_thresholds {
  |                       + scale_in  = 20
  |                       + scale_out = 80
  |                     }
  |                 }
  |             }
  | 
  |             # (1 unchanged block hidden)
  |         }
  | 
  |         # (1 unchanged block hidden)
  |     }
  | 
  | Plan: 0 to add, 1 to change, 0 to destroy.

I didn't see other errors.

@varshatumburu
Copy link
Contributor Author

Hello, @varshatumburu , I didn't update the resource. Instead, I created the resource.

This is the request:

POST /v1/projects/ci-test-project-188019/locations/me-west1-b/privateClouds?alt=json&privateCloudId=tf-test-sample-pcer48vrygfc HTTP/1.1
Host: vmwareengine.googleapis.com
User-Agent: Terraform/1.8.3 (+https://www.terraform.io) Terraform-Plugin-SDK/2.33.0 terraform-provider-google-

{
 "description": "sample updated description",
 "managementCluster": {
  "autoscalingSettings": {
   "autoscalingPolicies": {
    "autoscaling-policy": {
     "consumedMemoryThresholds": {
      "scaleIn": 20,
      "scaleOut": 75
     },
     "cpuThresholds": {
      "scaleIn": 15,
      "scaleOut": 80
     },
     "nodeTypeId": "standard-72",
     "scaleOutSize": 1,
     "storageThresholds": {
      "scaleIn": 20,
      "scaleOut": 80
     }
    }
   },
   "maxClusterNodeCount": 8,
   "minClusterNodeCount": 3
  },
  "clusterId": "tf-test-sample-mgmt-cluster-custom-core-counter48vrygfc",
  "nodeTypeConfigs": {
   "standard-72": {
    "customCoreCount": 32,
    "nodeCount": 3
   }
  }
 },
 "networkConfig": {
  "managementCidr": "192.168.0.0/24",
  "vmwareEngineNetwork": "projects/ci-test-project-188019/locations/global/vmwareEngineNetworks/tf-test-pc-nw-er48vrygfc"
 }
}

The error I got for the test is that

error=
  | After applying this test step, the plan was not empty.
  | stdout:
  | 
  | 
  | Terraform used the selected providers to generate the following execution
  | plan. Resource actions are indicated with the following symbols:
  |   ~ update in-place
  |  <= read (data resources)
  | 
  | Terraform will perform the following actions:
  | 
  |   # data.google_vmwareengine_nsx_credentials.nsx-ds will be read during apply
  |   # (depends on a resource or a module with changes pending)
  |  <= data "google_vmwareengine_nsx_credentials" "nsx-ds" {
  |       + id       = (known after apply)
  |       + parent   = "projects/ci-test-project-188019/locations/me-west1-b/privateClouds/tf-test-sample-pcer48vrygfc"
  |       + password = (known after apply)
  |       + username = (known after apply)
  |     }
  | 
  |   # data.google_vmwareengine_private_cloud.ds will be read during apply
  |   # (depends on a resource or a module with changes pending)
  |  <= data "google_vmwareengine_private_cloud" "ds" {
  |       + deletion_delay_hours              = (known after apply)
  |       + description                       = (known after apply)
  |       + hcx                               = (known after apply)
  |       + id                                = (known after apply)
  |       + location                          = "me-west1-b"
  |       + management_cluster                = (known after apply)
  |       + name                              = "tf-test-sample-pcer48vrygfc"
  |       + network_config                    = (known after apply)
  |       + nsx                               = (known after apply)
  |       + send_deletion_delay_hours_if_zero = (known after apply)
  |       + state                             = (known after apply)
  |       + type                              = (known after apply)
  |       + uid                               = (known after apply)
  |       + vcenter                           = (known after apply)
  |     }
  | 
  |   # data.google_vmwareengine_vcenter_credentials.vcenter-ds will be read during apply
  |   # (depends on a resource or a module with changes pending)
  |  <= data "google_vmwareengine_vcenter_credentials" "vcenter-ds" {
  |       + id       = (known after apply)
  |       + parent   = "projects/ci-test-project-188019/locations/me-west1-b/privateClouds/tf-test-sample-pcer48vrygfc"
  |       + password = (known after apply)
  |       + username = (known after apply)
  |     }
  | 
  |   # google_vmwareengine_private_cloud.vmw-engine-pc will be updated in-place
  |   ~ resource "google_vmwareengine_private_cloud" "vmw-engine-pc" {
  |         id                                = "projects/ci-test-project-188019/locations/me-west1-b/privateClouds/tf-test-sample-pcer48vrygfc"
  |         name                              = "tf-test-sample-pcer48vrygfc"
  |         # (10 unchanged attributes hidden)
  | 
  |       ~ management_cluster {
  |             # (1 unchanged attribute hidden)
  | 
  |           + autoscaling_settings {
  |               + max_cluster_node_count = 8
  |               + min_cluster_node_count = 3
  | 
  |               + autoscaling_policies {
  |                   + autoscale_policy_id = "autoscaling-policy"
  |                   + node_type_id        = "standard-72"
  |                   + scale_out_size      = 1
  | 
  |                   + consumed_memory_thresholds {
  |                       + scale_in  = 20
  |                       + scale_out = 75
  |                     }
  | 
  |                   + cpu_thresholds {
  |                       + scale_in  = 15
  |                       + scale_out = 80
  |                     }
  | 
  |                   + storage_thresholds {
  |                       + scale_in  = 20
  |                       + scale_out = 80
  |                     }
  |                 }
  |             }
  | 
  |             # (1 unchanged block hidden)
  |         }
  | 
  |         # (1 unchanged block hidden)
  |     }
  | 
  | Plan: 0 to add, 1 to change, 0 to destroy.

I didn't see other errors.

Autoscaling settings will not get added to the cluster without cool down period. Although some are optional fields in the proto, all fields (policy, min, max node count, cool down period) are mandatory for successful addition of autoscaling settings. Please retry by adding cool down period and let me know if you are facing the same issue.

@zli82016
Copy link
Member

Autoscaling settings will not get added to the cluster without cool down period. Although some are optional fields in the proto, all fields (policy, min, max node count, cool down period) are mandatory for successful addition of autoscaling settings. Please retry by adding cool down period and let me know if you are facing the same issue.

That makes sense. Do you have any suggestion how long the cool down period should be? Thanks.

@modular-magician
Copy link
Collaborator

Hi there, I'm the Modular magician. I've detected the following information about your changes:

Diff report

Your PR generated some diffs in downstreams - here they are.

google provider: Diff ( 3 files changed, 870 insertions(+), 5 deletions(-))
google-beta provider: Diff ( 3 files changed, 870 insertions(+), 5 deletions(-))
terraform-google-conversion: Diff ( 1 file changed, 222 insertions(+))

@varshatumburu
Copy link
Contributor Author

varshatumburu commented Oct 25, 2024

Post_create is needed .

Hi @zli82016 , I've added post_create file as requested and tested creation with autoscale settings at gpaste/5982018759557120

@modular-magician
Copy link
Collaborator

Tests analytics

Total tests: 14
Passed tests: 11
Skipped tests: 2
Affected tests: 1

Click here to see the affected service packages
  • vmwareengine

Action taken

Found 1 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests
  • TestAccVmwareengineExternalAddress_vmwareEngineExternalAddressUpdate

Get to know how VCR tests work

@modular-magician
Copy link
Collaborator

Hi there, I'm the Modular magician. I've detected the following information about your changes:

Diff report

Your PR generated some diffs in downstreams - here they are.

google provider: Diff ( 3 files changed, 887 insertions(+), 6 deletions(-))
google-beta provider: Diff ( 3 files changed, 887 insertions(+), 6 deletions(-))
terraform-google-conversion: Diff ( 1 file changed, 222 insertions(+))

@modular-magician
Copy link
Collaborator

Hi there, I'm the Modular magician. I've detected the following information about your changes:

Diff report

Your PR generated some diffs in downstreams - here they are.

google provider: Diff ( 3 files changed, 883 insertions(+), 6 deletions(-))
google-beta provider: Diff ( 3 files changed, 883 insertions(+), 6 deletions(-))
terraform-google-conversion: Diff ( 1 file changed, 222 insertions(+))

@modular-magician
Copy link
Collaborator

Tests analytics

Total tests: 14
Passed tests: 11
Skipped tests: 2
Affected tests: 1

Click here to see the affected service packages
  • vmwareengine

Action taken

Found 1 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests
  • TestAccVmwareengineExternalAddress_vmwareEngineExternalAddressUpdate

Get to know how VCR tests work

1 similar comment
@modular-magician
Copy link
Collaborator

Tests analytics

Total tests: 14
Passed tests: 11
Skipped tests: 2
Affected tests: 1

Click here to see the affected service packages
  • vmwareengine

Action taken

Found 1 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests
  • TestAccVmwareengineExternalAddress_vmwareEngineExternalAddressUpdate

Get to know how VCR tests work

@modular-magician
Copy link
Collaborator

🟢 Tests passed during RECORDING mode:
TestAccVmwareengineExternalAddress_vmwareEngineExternalAddressUpdate [Debug log]

🟢 No issues found for passed tests after REPLAYING rerun.


🟢 All tests passed!

View the build log or the debug log for each test

@modular-magician
Copy link
Collaborator

🟢 Tests passed during RECORDING mode:
TestAccVmwareengineExternalAddress_vmwareEngineExternalAddressUpdate [Debug log]

🟢 No issues found for passed tests after REPLAYING rerun.


🟢 All tests passed!

View the build log or the debug log for each test

@modular-magician
Copy link
Collaborator

Hi there, I'm the Modular magician. I've detected the following information about your changes:

Diff report

Your PR generated some diffs in downstreams - here they are.

google provider: Diff ( 3 files changed, 883 insertions(+), 6 deletions(-))
google-beta provider: Diff ( 3 files changed, 883 insertions(+), 6 deletions(-))
terraform-google-conversion: Diff ( 1 file changed, 222 insertions(+))

@modular-magician
Copy link
Collaborator

Tests analytics

Total tests: 14
Passed tests: 12
Skipped tests: 2
Affected tests: 0

Click here to see the affected service packages
  • vmwareengine

🟢 All tests passed!

View the build log

Copy link
Member

@zli82016 zli82016 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants