titiler_url and titiler_vpce_dns_regional outputs not populated when using filmdrop-titiler profile

[matthewhanson]

Summary

When deploying with deploy_filmdrop_titiler = true, the titiler_url an titiler_vpce_dns_regional outputs in profiles/core return empty values ("" and null respectively), even though the standard FilmDrop TiTiler module is successfully deployed and its own outputs are available.

Root Cause

The two affected outputs in profiles/core/outputs.tf only handle the
deploy_titiler (mosaic) path:

output "titiler_url" {
  value = var.deploy_titiler ? module.titiler[0].titiler_url : ""
}

output "titiler_vpce_dns_regional" {
  value = var.deploy_titiler ? module.titiler[0].titiler_vpce_dns_regional : null
}

When deploy_titiler = false and deploy_filmdrop_titiler = true, both expressions fall through to the empty/null default. The filmdrop-titiler profile already exposes titiler_url and titiler_vpce_dns_regional in its own outputs.tf — the core profile just isn't passing them through.

Impact

Any downstream consumer that uses profiles/core and reads titiler_url or titiler_vpce_dns_regional — for example to wire a UI config or set up cross-module dependencies — will silently receive empty values when the standard filmdrop-titiler path is chosen.

Expected Fix

Extend both conditionals to fall through to the filmdrop-titiler module outputs:

 output "titiler_url" {
   value = var.deploy_titiler ? module.titiler[0].titiler_url : var.deploy_filmdrop_titiler ? module.filmdrop-titiler[0].titiler_url : ""
 }
 
 output "titiler_vpce_dns_regional" {
   value = var.deploy_titiler ? module.titiler[0].titiler_vpce_dns_regional : var.deploy_filmdrop_titiler ? module.filmdrop-titiler[0].titiler_vpce_dns_regional : null
 }