fix: refuse new stacks with shared endpoint hostnames, add deployments delete --forget

[alongubkin]

Summary

• Refuse new stacks whose public endpoints share a hostname. Generated hostnames are <hostLabel>.<deployment domain>, so two resources that both expose an endpoint named api collide in every deployment. alien build and alien release accepted such stacks. A new build-time check rejects them and names both resources.
  • The check is registered as build-time only (new PreflightRegistry::add_build_time_check). Deployment-time and template preflights do not run it, so stacks released before this check keep deploying and updating.
  • Two enabledWhen-gated resources may be alternatives chosen at deploy time, so they may still share a host label.
• alien deployments delete <id> --forget. Sends action: forget, which removes only the deployment record. It is for deployments whose resources are already gone (for example, a deleted CloudFormation stack or Helm release) but that stay stuck. The server already supports this action and limits it to admins.

Testing

• cargo test -p alien-preflights (392 + integration tests pass). New tests in compile_time/unique_endpoint_host_labels.rs:
  • the build-time pipeline refuses two resources with endpoint api and names both;
  • run_compile_time_checks (used by deployment-time preflights) and run_template_preflights still accept that same stack, which is what keeps existing releases updatable;
  • host-label overrides across containers and workers, apex labels, gated alternatives, TCP endpoints.
• cargo test -p alien-cli --lib delete_forget: drives delete_deployment_task against a loopback manager and asserts the exact request bodies (forget, then cleanup).

🤖 Generated with Claude Code

[greptile-apps]

Confidence Score: 5/5

[Critical risk] Adds validation that blocks new stack releases with conflicting endpoint hostnames.

The PR appears safe to merge; no outstanding finding or actionable new regression was established.

Summary

The PR adds build-time and manager-API checks for shared endpoint hostnames on supported platforms, plus alien deployments delete --forget to remove a deployment record without resource cleanup.

• Previously released stacks remain outside the new deployment-time checks.
• The CLI no longer suggests fetching a deployment after forgetting it.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart LR
  A[Build new stack] --> B[Build-time hostname check]
  C[POST /v1/releases] --> D[Parse platform stacks]
  D --> E[Hostname check]
  E --> F[Store new release]
  G[Deploy existing release] --> H[Deployment-time checks without new hostname check]

Loading

_{Reviews (2) · Last reviewed commit: "fix: refuse shared endpoint hostnames in..."}

[alongubkin]

@greptileai review