@rebasepro/cli 0.12.1-canary.g4e7bcbf → 0.12.1-canary.g52d71ee

package/dist/commands/cloud/context.d.ts

@@ -24,7 +24,32 @@ export declare function requireClient(rawArgs: string[]): Promise<{
     client: CloudClient;
     url: string;
 }>;
+/** One place a deploy can actually land, as the control plane describes it. */
+export interface DeployTarget {
+    clusterId?: string | null;
+    provider: string;
+    region?: string;
+    label?: string;
+    baseDomain?: string;
+}
+export interface PlatformConfig {
+    tenantBaseDomain?: string;
+    deployTargets?: DeployTarget[];
+}
+export declare function fetchPlatformConfig(client: CloudClient, url: string): Promise<PlatformConfig | undefined>;
+/**
+ * The base domain tenant projects are served at, derived from the same
+ * TENANT_BASE_DOMAIN the ingress and the console read (see
+ * saas/backend/src/utils/tenant-domain.ts).
+ */
 export declare function fetchTenantBaseDomain(client: CloudClient, url: string): Promise<string | undefined>;
+/**
+ * The infrastructure a deploy for this control plane would ACTUALLY use, in the
+ * resolver's own preference order (saas/backend/src/k8s/resolve.ts).
+ *
+ * @returns the targets, or `undefined` when the control plane cannot say.
+ */
+export declare function fetchDeployTargets(client: CloudClient, url: string): Promise<DeployTarget[] | undefined>;
 /**
  * Public host for a project — `<subdomain>.<base>`, or the bare subdomain when
  * the base domain is unknown.

package/dist/commands/cloud/projects.d.ts

@@ -1,5 +1,36 @@
-import { type CloudClient } from "./context";
+import { type DeployTarget, type CloudClient } from "./context";
 export declare function listProjects(rawArgs: string[]): Promise<void>;
+/**
+ * Where this project says it runs.
+ *
+ * `provider`/`region` are a *request*: no code downstream reads them to pick a
+ * deploy target — that comes from the project's cluster record or the ambient
+ * in-cluster context (saas/backend/src/k8s/resolve.ts). So a wrong value here is
+ * never contradicted by a failure; it just sits in the record. The CLI used to
+ * default to `hetzner`/`nbg1` unconditionally, which is how projects running on
+ * our GKE cluster came to describe themselves as Hetzner in the console — and
+ * `provider` is half the Stripe compute lookup key (`compute_<provider>_<vmSize>`),
+ * so that is a mispricing, not a cosmetic slip.
+ *
+ * The control plane already publishes the infrastructure that actually exists,
+ * and the console's create wizard reads it. Ask the same question here.
+ *
+ * Exported for tests: the decision is pure, so it can be pinned without a
+ * control plane. The fetching and the exit live in `resolveRequestedTarget`.
+ *
+ * @param requested `--provider`, if the caller named one. An explicit flag wins:
+ *   it is the caller stating intent, and `deploy` corrects the record anyway.
+ * @param targets What the control plane says exists, or `undefined` when it
+ *   cannot say — an older deployment with no `platform-config`, or a failed
+ *   request. That is different from an empty list, which is a control plane
+ *   stating it has no infrastructure at all.
+ * @returns the target to record, or `null` when the control plane answered that
+ *   there is none.
+ */
+export declare function chooseRequestedTarget(requested: string | undefined, targets: DeployTarget[] | undefined): {
+    provider: string;
+    region?: string;
+} | null;
 export declare function createProject(rawArgs: string[]): Promise<void>;
 export declare function projectInfo(rawArgs: string[], projectRef: string): Promise<void>;
 export declare function deleteProject(rawArgs: string[], projectRef: string): Promise<void>;

package/dist/commands/telemetry.d.ts

@@ -0,0 +1,9 @@
+/**
+ * `rebase telemetry` — the command that makes the rest of it inspectable.
+ *
+ * The whole subsystem asks for trust it cannot otherwise earn, and the cheapest
+ * way to earn it is to stop describing the payload and print it. `show` runs
+ * the same builder the sender uses, so what appears here is what would go, not
+ * a documentation comment that quietly fell out of date two releases ago.
+ */
+export declare function telemetryCommand(rawArgs: string[]): Promise<void>;