Problem

Currently, adding a domain via the endpoint only registers the domain. A separate deployment is required afterward to:

• Activate the domain
• Provision the SSL certificate

This introduces unnecessary coupling between domain management and deployment, and requires an additional manual/API step.

Why this is an issue

Adding a domain is conceptually a configuration change, not a deployment concern It creates redundant operational overhead (extra request / deployment trigger) Tenants indirectly triggering deployments by adding domains is undesirable.

Context

We are running a tenant-aware application where tenants can add their own domains. In this setup:

• Domain management should be self-contained
• Infrastructure concerns (like SSL provisioning) should be handled automatically
• Tenants should not trigger deployments as a side effect of adding a domain

Proposed improvement

When a domain is added via the endpoint:

• The domain is automatically activated
• An SSL certificate is automatically provisioned

All of the above should happen without requiring a separate deployment step.