add Vue service to DNS load balancer config

[serglom21]

Description

Adding Vue domain to load balancer config as part of Vue Demo Refresh (#994 )

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
empower	Ignored		Apr 10, 2026 0:39am

[codecov]

⚠️ JUnit XML file not found

The CLI was unable to find any JUnit XML files to upload.
For more help, visit our troubleshooting guide.

[sentry]

Bug: The DNS configuration template references the variable VUE_SUBDOMAIN, which is not defined in any environment files, causing the deployment script to fail.
_{Severity: CRITICAL}

Suggested Fix

Define the VUE_SUBDOMAIN variable in the relevant environment configuration files, such as production.env and staging.env. Follow the existing pattern for other services, for example, by adding VUE_SUBDOMAIN=vue to production.env and VUE_SUBDOMAIN=staging-vue to staging.env.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: _dns/config.yaml.template#L52-L53

Potential issue: The new DNS configuration in `_dns/config.yaml.template` references the
variable `${VUE_SUBDOMAIN}`. However, this variable is not defined in any environment
configuration files (e.g., `production.env`, `staging.env`). The deployment script
utilizes `envsubst.sh` with a strict mode (`--strict-allow-empty`) that explicitly fails
when a variable is undefined. As a result, attempting to deploy the `_dns` project will
cause the deployment script to terminate with an error, preventing the entire DNS load
balancer configuration from being applied. This affects all services that rely on this
DNS configuration, not just the new Vue service.

_{Did we get this right? 👍 / 👎 to inform future reviews.}

[maxkosty]

please update staging.env, production.env and .local.env.base
#994 only adds vars to staging.env
make sure to follow the current pattern with _SUBDOMAIN e.g.

empower/production.env

Lines 107 to 112 in 991204b

	ANGULAR_DSN=${__GCP_SECRET__(ANGULAR_DSN_SANDBOX_MIRROR)}
	ANGULAR_SENTRY_PROJECT=frontend-${ANGULAR_SUBDOMAIN}
	ANGULAR_APP_ENGINE_SERVICE=${ANGULAR_SUBDOMAIN}
	ANGULAR_SENTRY_ENVIRONMENT=production
	ANGULAR_RELEASE=empower.${ANGULAR_SUBDOMAIN}@${__DYNAMIC_VERSION__}
	ANGULAR_SUBDOMAIN=angular

(what Seer comment below is referring to).

otherwise looks good!