You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request.
Please do not leave +1 or me too comments, they generate extra noise for issue followers and do not help prioritize the request.
If you are interested in working on this issue or have submitted a pull request, please leave a comment.
If an issue is assigned to a user, that user is claiming responsibility for the issue.
Customers working with a Google Technical Account Manager or Customer Engineer can ask them to reach out internally to expedite investigation and resolution of this issue.
There was an unknown defect in the code for handling errors in the google_compute_resize_request resource, which was only found when an acceptance test panicked when handling an error caused by the test environment.
If possible, we should write an acceptance test that triggers an error when creating a google_compute_resize_request resource to show that these fields behave as expected.
Community Note
Description
See #19917
There was an unknown defect in the code for handling errors in the google_compute_resize_request resource, which was only found when an acceptance test panicked when handling an error caused by the test environment.
If possible, we should write an acceptance test that triggers an error when creating a
google_compute_resize_request
resource to show that these fields behave as expected.New or Affected Resource(s)
Potential Terraform Configuration
N/A
References
#19917
b/377316369
The text was updated successfully, but these errors were encountered: