@ts-cloud/core 0.12.10 → 0.12.12

package/dist/drivers/types.d.ts

@@ -1,5 +1,5 @@
 import type { CloudConfig, EnvironmentType, SiteConfig } from '../types';
-export type CloudProviderName = 'aws' | 'hetzner';
+export type CloudProviderName = 'aws' | 'hetzner' | 'ssh';
 /**
  * Exhaustive provider map. Provider-specific contract tests key off this type,
  * so adding a provider without adding its resilience coverage is a type error.
@@ -36,6 +36,13 @@ export interface ComputeStackOutputs {
     servicesPrivateIp?: string;
     /** Fleet: public IP of the load balancer fronting the app servers. */
     loadBalancerIp?: string;
+    /**
+     * On-box path to the LAN certificate authority's certificate, for a host
+     * whose gateway signs its own TLS (`ssh.lan.tls: 'local-ca'`). Reported so a
+     * caller can fetch the file and trust it on a laptop or a phone; absent for
+     * every publicly-resolvable deploy, which uses Let's Encrypt instead.
+     */
+    lanCaCertPath?: string;
 }
 export interface RemoteDeployInstanceResult {
     instanceId: string;
@@ -172,6 +179,12 @@ export interface DeploySiteReleaseResult {
 }
 /**
  * Resolve the configured cloud provider. Defaults to AWS for backward compatibility.
- * Environment-based auto-detection is handled when constructing the Hetzner driver.
+ *
+ * An explicit `cloud.provider` always wins. Without one, the config itself is
+ * the tell: a project that lists `ssh.hosts` is deploying to hosts it already
+ * owns, and a project with a Hetzner token is deploying to Hetzner. The ssh
+ * provider is never inferred from the environment alone (`TS_CLOUD_SSH_HOST`
+ * is a per-machine override, not a statement of intent); the Hetzner token
+ * check keeps the behaviour it always had.
  */
 export declare function resolveCloudProvider(config: CloudConfig): CloudProviderName;