openvidu/openvidu-deployment/community/singlenode/gcp
Carlos Ruiz Ballesteros 96b0a255f6
deployment: use the public IP directly instead of sslip.io for TLS (#904)
When no domain is provided, cloud templates now use the discovered public IP
directly as the domain instead of building an openvidu-<random>-<ip>.sslip.io
name, relying on Let's Encrypt IP certificates (handled by the installer/Caddy).
Public IP acquisition is unchanged everywhere; only the domain construction changed.

- AWS CloudFormation: derive the bare IP from the already-fetched public-hostname.
- GCP Terraform: use the instance/NLB external IP already obtained.
- Azure Bicep: use the public IP from get_public_ip.sh; ARM JSON regenerated
  from Bicep, and createUiDefinition tooltips updated.

HA on AWS is unchanged: it uses an ACM certificate (which cannot cover a bare IP).

Assisted-by: Anthropic - Claude Opus 4.8
2026-07-02 17:21:42 +02:00
..
output.tf Add Terraform configuration for OpenVidu deployment on GCP 2025-10-29 18:26:56 +01:00
tf-gpc-openvidu-singlenode.tf deployment: use the public IP directly instead of sslip.io for TLS (#904) 2026-07-02 17:21:42 +02:00
variables.tf deployment: use the public IP directly instead of sslip.io for TLS (#904) 2026-07-02 17:21:42 +02:00
versions.tf openvidu-deployment: GCP - Added zone dependency becasue its required 2025-12-10 18:42:57 +01:00