From e8e2a5fa569b64c16cd923ad4eb080f253880501 Mon Sep 17 00:00:00 2001
From: Graham McIntire <graham@mcintire.me>
Date: Wed, 18 Mar 2026 09:33:22 -0500
Subject: [PATCH] fix site lat/lng inconsistent result after apply

mark latitude and longitude as Computed in addition to Optional so
the provider accepts server-set values (geocoding, UI) when the user
omits them from config
---
 internal/provider/site_resource.go | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/internal/provider/site_resource.go b/internal/provider/site_resource.go
index b719595..40b787a 100644
--- a/internal/provider/site_resource.go
+++ b/internal/provider/site_resource.go
@@ -68,10 +68,12 @@ func (r *SiteResource) Schema(ctx context.Context, req resource.SchemaRequest, r
 			"latitude": schema.Float64Attribute{
 				Description: "The latitude of the site (-90 to 90).",
 				Optional:    true,
+				Computed:    true,
 			},
 			"longitude": schema.Float64Attribute{
 				Description: "The longitude of the site (-180 to 180).",
 				Optional:    true,
+				Computed:    true,
 			},
 			"snmp_community": schema.StringAttribute{
 				Description: "The default SNMP community string for devices at this site.",