Updates to `resource meraki_networks` seems to trigger updates to resources using its output.

[finkjordanj]

Prerequisites

• [X] Have you tested the operation in the API directly?
• [X] Do you have the latest Terraform provider version?
• [X] Review the compatibility matrix before opening an issue.

Describe the bug When updating the notes of the meraki_networks resource

resource "meraki_networks" "this" {
  name            = var.site_name
  notes           = var.site_notes
  organization_id = var.org_id
  product_types   = var.network_hardware

  lifecycle {
    ignore_changes = [tags]
  }
}

Any subsequent resources I leverage the output of the network_id (id) output appears to be triggering a recompute of all the resources for the network_id input.

Expected behavior If the only update to the meraki_networks is the notes, then that resource would update, while all the subsequent using that ID as its input, will remain unaffected.

Screenshots This is the change showing my update to in theory just the notes on the resource.

This shows my terraform plan out showing all my nested resources in my module having to do computed update?

Debug The major debug that appears to be related is most the resources give this output or similar to their specific resource in question.

2024-11-20T15:48:17.690Z [DEBUG] provider.terraform-provider-meraki_v0.2.12-alpha: Marking Computed attributes with null configuration values as unknown (known after apply) in the plan to prevent potential Terraform errors: @caller=github.com/hashicorp/terraform-plugin-framework@v1.11.0/internal/fwserver/server_planresourcechange.go:217 @module=sdk.framework tf_provider_addr=registry.terraform.io/CiscoDevNet/meraki tf_req_id=706fd5ed-c7ce-933a-1812-1d2ccab161b8 tf_resource_type=meraki_networks_appliance_firewall_port_forwarding_rules tf_rpc=PlanResourceChange timestamp=2024-11-20T15:48:17.690Z

Environment (please complete the following information):

• Terraform version: 1.9.8
• Meraki provider version: 0.2.12-alpha
• OS Version: ubuntu 22.04

Additional context Add any other context about the problem here.