# group_id/member_id are cross-resource references to a group and user
# created in the same plan, so they're unresolved pre-apply and absent from
# planned_values.values in negative3.json (a real create plan for this exact
# configuration). The rule confirms via
# _dd_tfplan_meta.configuration_expressions that both references target this
# group (tf_lib.references_same_target) and that member_id was actually
# configured, so it correctly stays silent instead of treating this group as
# having no members.
resource"databricks_group""negative3_group"{display_name="Some Group"allow_cluster_create=trueallow_instance_pool_create=true}resource"databricks_user""negative3_user"{user_name="someone@example.com"}resource"databricks_group_member""negative3_member"{group_id=databricks_group.negative3_group.idmember_id=databricks_user.negative3_user.id}