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.
resource"google_service_account""default" {
account_id="my-custom-sa"display_name="Custom SA for VM Instance"
}
resource"google_compute_instance""default" {
name="my-instance"machine_type="n2-standard-2"zone="us-central1-a"tags=["foo", "bar"]
boot_disk {
initialize_params {
image="debian-cloud/debian-11"labels={
my_label ="value"
}
}
}
// Local SSD diskscratch_disk {
interface="NVME"
}
network_interface {
network="default"stack_type="IPV4_ONLY"access_config {
// Ephemeral public IP
}
}
metadata={
foo ="bar"
}
metadata_startup_script="echo hi > /test.txt"service_account {
# Google recommends custom service accounts that have cloud-platform scope and permissions granted via IAM Roles.email=google_service_account.default.emailscopes=["cloud-platform"]
}
}
Can update network_interface.stack_type from IPV4_ONLY to IPV4_IPV6
Actual Behavior
Cannot update network_interface.stack_type from IPV4_ONLY to IPV4_IPV6
Steps to reproduce
terraform apply
Change network_interface.stack_type from IPV4_ONLY to IPV4_IPV6 in the config
3.terraform apply => you'll see a plan to update the field, but after applying the plan the state is unchanged
terraform apply => there is still a plan to update the field
Important Factoids
When the update happens there is never a PATCH request sent to the compute API to update the resource. It appears a defect in the provider code stops the change happening.
References
No response
b/324394301
The text was updated successfully, but these errors were encountered:
I'm going to lock this issue 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 similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Community Note
to expedite investigation and resolution of this issue.
Terraform Version
Terraform v1.5.7
on darwin_arm64
Affected Resource(s)
Terraform Configuration
Debug Output
https://gist.github.com/SarahFrench/c15d40e63d01d15505e8578656bccff7
Expected Behavior
Can update network_interface.stack_type from
IPV4_ONLY
toIPV4_IPV6
Actual Behavior
Cannot update network_interface.stack_type from
IPV4_ONLY
toIPV4_IPV6
Steps to reproduce
terraform apply
IPV4_ONLY
toIPV4_IPV6
in the config3.
terraform apply
=> you'll see a plan to update the field, but after applying the plan the state is unchangedterraform apply
=> there is still a plan to update the fieldImportant Factoids
When the update happens there is never a PATCH request sent to the compute API to update the resource. It appears a defect in the provider code stops the change happening.
References
No response
b/324394301
The text was updated successfully, but these errors were encountered: