Single-page app for reporting Gilly's location.

• Attempts to collect reporter geolocation when the page loads
• Falls back to map selection if location access is unavailable
• Lets the reporter submit contact details/notes
• Stores reports in SQL table GillyTracker.DogSightingReports
• Provides an admin-only sightings page at /admin/sightings
• Uses Microsoft Entra sign-in for admins and only allows users in PetTrackerAdmins

Set these values for the backend (for local development use user-secrets or environment variables):

• Authentication:Microsoft:TenantId
• Authentication:Microsoft:ClientId
• Authentication:Microsoft:ClientSecret
• Authorization:PetTrackerAdminsGroupObjectId (the Entra object ID for PetTrackerAdmins)

The backend accepts these keys in : (Authentication:Microsoft:TenantId), __ (Authentication__Microsoft__TenantId), and -- (Authentication--Microsoft--TenantId) formats so values can come from standard app settings, environment variables, or Key Vault-style secret names.

dotnet test --project /home/runner/work/GillyTracker/GillyTracker/GillyTracker.Core.Tests/GillyTracker.Core.Tests.csproj
cd /home/runner/work/GillyTracker/GillyTracker/GillyTracker.Web
pnpm install --frozen-lockfile
pnpm lint
pnpm build

Terraform is configured to use existing Azure resources:

• Resource Group: KebooDev
• ACR: keboodevacr.azurecr.io
• Container App Environment: keboodev-env
• SQL Server and database are discovered via Terraform data sources in the existing resource group
• Frontend hosting is provisioned as an Azure Static Web App, and backend CORS allows that origin
• Frontend production builds use Terraform backend_url
• The deploy-infrastructure workflow expects repository secrets GITHUB_ACTIONS_APP_OBJECT_ID and GITHUB_ACTIONS_INFRA_OBJECT_ID for database user principal IDs

Terraform now provisions an Azure Key Vault in the deployment resource group. Terraform also creates the backend Entra app registration and writes these Key Vault secrets automatically:

• Authentication--Microsoft--TenantId
• Authentication--Microsoft--ClientId
• Authentication--Microsoft--ClientSecret
• Authorization--PetTrackerAdminsGroupObjectId

The backend reads Key Vault directly as an IConfiguration source using its managed identity. Terraform sets KeyVault__VaultUri on the container app so runtime configuration resolves those secrets automatically.

Apply infrastructure changes:

terraform -chdir=Infra plan
terraform -chdir=Infra apply -auto-approve