google_netapp_volume showing diff for labels, restricted_actions, smb_settings

[imrannayer]

Community Note

• 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.

Terraform Version

1.6

Affected Resource(s)

google_netapp_volume

Terraform Configuration

Debug Output

No response

Expected Behavior

It should not show diff

Actual Behavior

It is showing diff in out on next execution

 ~ storage_volumes      = {
     ~ test-volume-1 = {
           id                 = "projects/ci-netapp-volume-e8c4/locations/us-central1/volumes/test-volume-1"
         ~ labels             = null -> {}
           name               = "test-volume-1"
         ~ restricted_actions = null -> []
         ~ smb_settings       = null -> []
           # (26 unchanged attributes hidden)
       }
     ~ test-volume-2 = {
           id                 = "projects/ci-netapp-volume-e8c4/locations/us-central1/volumes/test-volume-2"
         ~ labels             = null -> {}
           name               = "test-volume-2"
         ~ restricted_actions = null -> []
         ~ smb_settings       = null -> []
           # (26 unchanged attributes hidden)
       }
   }

Steps to reproduce

1. terraform apply
2. terraform apply

Important Factoids

No response

References

No response

b/323501879

[Mehul3217]

This was not reproduced on local.

random_pet.suffix: Refreshing state... [id=allowing-pipefish]
google_compute_network.peering_network: Refreshing state... [id=projects/goyalmehul-netapp/global/networks/test-network-allowing-pipefish]
google_compute_global_address.private_ip_alloc: Refreshing state... [id=projects/goyalmehul-netapp/global/addresses/test-address-allowing-pipefish]
google_netapp_storage_pool.test_pool-1: Refreshing state... [id=projects/goyalmehul-netapp/locations/us-central1/storagePools/test-pool-1-allowing-pipefish]
google_netapp_storage_pool.test_pool-2: Refreshing state... [id=projects/goyalmehul-netapp/locations/us-central1/storagePools/test2-pool-2-allowing-pipefish]
google_service_networking_connection.default: Refreshing state... [id=projects%2Fgoyalmehul-netapp%2Fglobal%2Fnetworks%2Ftest-network-allowing-pipefish:netapp.servicenetworking.goog]
google_compute_network_peering_routes_config.route_updates: Refreshing state... [id=projects/goyalmehul-netapp/global/networks/test-network-allowing-pipefish/networkPeerings/sn-netapp-prod]

No changes. Your infrastructure matches the configuration.

Terraform has compared your real infrastructure against your configuration and found no differences, so no changes are needed.

Apply complete! Resources: 0 added, 0 changed, 0 destroyed.

Configs used:

 project = "test-project"
  name = "test-pool-1"
  location = "us-central1"
  service_level = "PREMIUM"
  capacity_gib = "2048"
  network = google_compute_network.peering_network.id
  description      = "description"
  labels           = {"purpose": "testing"}
  ldap_enabled     = false
  active_directory = null

  project = "test-project"
  name = "test-pool-2"
  location = "us-central1"
  service_level = "PREMIUM"
  capacity_gib = "2048"
  network = google_compute_network.peering_network.id
  description      = "description"
  labels           = {"purpose": "testing"}
  ldap_enabled     = false
  active_directory = null

I think we can close this if it not occuring anymore.