@synteq/cli 0.1.6 → 1.1.1

package/dist/commands/function/deploy.d.ts

@@ -0,0 +1,64 @@
+import { BaseCommand } from "../../base/command.js";
+/**
+ * `synteq function deploy` — upload this directory's source and roll it out,
+ * or roll out a pre-built image with `--image <ref>`.
+ *
+ * Backend: POST /functions/{id}/deploys/source — the files inline when the
+ * tree fits the editor's 32-file shape (so the portal editor can reopen it),
+ * else a gzipped tarball (`sourceB64`) bounded only by the function's source
+ * caps (`maxSourceBytes` / `maxSourceFiles` on the row). The server decides the build path (Dockerfile / bundle) itself and
+ * returns the build row. The deploy then has two phases the CLI follows: the
+ * BUILD reaches succeeded/failed, then the status cron mints a RELEASE and
+ * flips it current once the function is live. `--image` is the apps
+ * `deploy --image` route, function-owned (POST /functions/{id}/deploys): no
+ * source, a pull Build the same two phases follow.
+ */
+export default class FunctionDeploy extends BaseCommand {
+    static apiKeyScope: string;
+    static description: string;
+    static examples: string[];
+    static args: {
+        target: import("@oclif/core/interfaces").Arg<string | undefined, Record<string, unknown>>;
+    };
+    static flags: {
+        name: import("@oclif/core/interfaces").OptionFlag<string | undefined, import("@oclif/core/interfaces").CustomOptions>;
+        create: import("@oclif/core/interfaces").OptionFlag<string | undefined, import("@oclif/core/interfaces").CustomOptions>;
+        runtime: import("@oclif/core/interfaces").OptionFlag<string | undefined, import("@oclif/core/interfaces").CustomOptions>;
+        plan: import("@oclif/core/interfaces").OptionFlag<string | undefined, import("@oclif/core/interfaces").CustomOptions>;
+        location: import("@oclif/core/interfaces").OptionFlag<string | undefined, import("@oclif/core/interfaces").CustomOptions>;
+        project: import("@oclif/core/interfaces").OptionFlag<string | undefined, import("@oclif/core/interfaces").CustomOptions>;
+        dir: import("@oclif/core/interfaces").OptionFlag<string | undefined, import("@oclif/core/interfaces").CustomOptions>;
+        image: import("@oclif/core/interfaces").OptionFlag<string | undefined, import("@oclif/core/interfaces").CustomOptions>;
+        "no-wait": import("@oclif/core/interfaces").BooleanFlag<boolean>;
+        "poll-interval": import("@oclif/core/interfaces").OptionFlag<number, import("@oclif/core/interfaces").CustomOptions>;
+        timeout: import("@oclif/core/interfaces").OptionFlag<number, import("@oclif/core/interfaces").CustomOptions>;
+        env: import("@oclif/core/interfaces").OptionFlag<string[] | undefined, import("@oclif/core/interfaces").CustomOptions>;
+        secret: import("@oclif/core/interfaces").OptionFlag<string[] | undefined, import("@oclif/core/interfaces").CustomOptions>;
+        cron: import("@oclif/core/interfaces").OptionFlag<string | undefined, import("@oclif/core/interfaces").CustomOptions>;
+        yes: import("@oclif/core/interfaces").BooleanFlag<boolean>;
+        "env-file": import("@oclif/core/interfaces").OptionFlag<string | undefined, import("@oclif/core/interfaces").CustomOptions>;
+    };
+    /** The argv `function init` runs with on a first deploy: --create's values
+     *  verbatim, else what the user picks. Runtime comes from the directory's
+     *  files when they say (init infers it too; passing it keeps the two in
+     *  step when the user overrides). */
+    private firstRunArgs;
+    /** Step 0 of the first run — the apps `pickOrCreateApp` shape: link one of
+     *  the project's functions, or null for "Create a new function…". No
+     *  functions at all goes straight to create. */
+    private pickExistingFunction;
+    /** The two optional steps after location on a created function: env vars
+     *  (the apps walkthrough's shape — confirm, then name → value → secret?
+     *  until a blank name) and a cron trigger (blank for none). Each is
+     *  skipped when its flags already answered it. */
+    private promptFirstRunExtras;
+    /** Set the env vars (same call `function env set` makes) and add the cron
+     *  trigger (same call `function cron add` makes) — before the build, so
+     *  the release it produces carries them. */
+    private applySetup;
+    run(): Promise<void>;
+    /** Steps 5+: print the build row (--no-wait) or follow the build and the
+     *  release it produces — in JSON mode too, with progress on stderr. Shared
+     *  by the source and image paths. */
+    private follow;
+}