@myapihq/sdk 2.28.0 → 2.28.2

package/dist/container.d.ts

@@ -51,9 +51,23 @@ export interface DeployResponse {
 }
 export declare function createContainer(apiKey: string, orgId: string, payload: CreatePayload): Promise<CreateResponse>;
 export declare function listContainers(apiKey: string, orgId: string): Promise<Container[]>;
-export declare function getContainer(apiKey: string, orgId: string, containerId: string): Promise<Container>;
-/** The result of an environment change. `env` is the RESULT of the merge, so a
- *  caller never has to GET afterwards to see what a PATCH did. */
+/**
+ * Reads a container. Environment VALUES come back as the string `"set"` unless
+ * `reveal` is passed — the names are always visible, the values are not.
+ *
+ * The redaction is right: this response used to return every secret in clear,
+ * and a customer keeps their document master key in it. But it shipped without
+ * a client that could ask for the values, so between that deploy and this
+ * change `container get` was the only way to read an env var back and it
+ * answered `"set"` for all of them. Setting a variable and verifying it are
+ * different operations, and only one of them worked.
+ *
+ * Two whole template literals rather than a concatenation: the coverage linter
+ * resolves the URL statically.
+ */
+export declare function getContainer(apiKey: string, orgId: string, containerId: string, opts?: {
+    reveal?: boolean;
+}): Promise<Container>;
 export interface EnvUpdate {
     set: string[];
     removed: string[];

package/dist/container.js

@@ -43,9 +43,36 @@ async function listContainers(apiKey, orgId) {
     // complete answer into a partial one.
     return (0, client_1.requestAll)(`${config_1.CONTAINER_BASE}/container/orgs/${encodeURIComponent(orgId)}/containers`, apiKey);
 }
-async function getContainer(apiKey, orgId, containerId) {
-    return (0, client_1.request)('GET', `${config_1.CONTAINER_BASE}/container/orgs/${encodeURIComponent(orgId)}/containers/${encodeURIComponent(containerId)}`, apiKey);
+/**
+ * Reads a container. Environment VALUES come back as the string `"set"` unless
+ * `reveal` is passed — the names are always visible, the values are not.
+ *
+ * The redaction is right: this response used to return every secret in clear,
+ * and a customer keeps their document master key in it. But it shipped without
+ * a client that could ask for the values, so between that deploy and this
+ * change `container get` was the only way to read an env var back and it
+ * answered `"set"` for all of them. Setting a variable and verifying it are
+ * different operations, and only one of them worked.
+ *
+ * Two whole template literals rather than a concatenation: the coverage linter
+ * resolves the URL statically.
+ */
+async function getContainer(apiKey, orgId, containerId, opts) {
+    const url = opts?.reveal
+        ? `${config_1.CONTAINER_BASE}/container/orgs/${encodeURIComponent(orgId)}/containers/${encodeURIComponent(containerId)}?reveal=true`
+        : `${config_1.CONTAINER_BASE}/container/orgs/${encodeURIComponent(orgId)}/containers/${encodeURIComponent(containerId)}`;
+    return (0, client_1.request)('GET', url, apiKey);
 }
+/** The result of an environment change. `env` is the RESULT of the merge, so a
+ *  caller never has to GET afterwards to see what a PATCH did. */
+/**
+ * Deadline for calls that roll a container revision.
+ *
+ * Five minutes because the platform advertises "~4 minutes" for a source build
+ * and a revision roll is the same machinery without the build step. The SDK's
+ * 120s default is a read timeout and is wrong for these.
+ */
+const REVISION_ROLL_TIMEOUT_MS = 300_000;
 /**
  * Change environment variables on an existing container.
  *
@@ -68,7 +95,15 @@ async function getContainer(apiKey, orgId, containerId) {
  * takes a patch rather than one named field.
  */
 async function updateContainer(apiKey, orgId, containerId, patch) {
-    return (0, client_1.request)('PATCH', `${config_1.CONTAINER_BASE}/container/orgs/${encodeURIComponent(orgId)}/containers/${encodeURIComponent(containerId)}`, apiKey, patch);
+    // A revision roll, not a metadata write: the server redeploys on the same
+    // image before answering. That regularly outlasts the SDK's 120s default —
+    // `container health-check` timed out at exactly 120000ms against a real
+    // container — and the CLI's own deploy text says a build is "typically ~4
+    // minutes", so the client was giving up at half the time it advertises.
+    //
+    // A timeout here is the worst kind of answer, because PATCH is not safely
+    // retryable: the caller cannot tell whether the change landed. Better to wait.
+    return (0, client_1.request)('PATCH', `${config_1.CONTAINER_BASE}/container/orgs/${encodeURIComponent(orgId)}/containers/${encodeURIComponent(containerId)}`, apiKey, patch, undefined, { timeoutMs: REVISION_ROLL_TIMEOUT_MS });
 }
 /** Environment-only shorthand for {@link updateContainer}. */
 async function updateContainerEnv(apiKey, orgId, containerId, env) {

package/dist/version.d.ts

@@ -1 +1 @@
-export declare const SDK_VERSION = "2.28.0";
+export declare const SDK_VERSION = "2.28.2";

package/dist/version.js

@@ -8,4 +8,4 @@ exports.SDK_VERSION = void 0;
 // Why a constant and not a package.json read: the SDK runs inside edge
 // functions (Cloudflare Workers), so it must not import node:fs. A literal
 // is the only version source that works in every runtime we ship to.
-exports.SDK_VERSION = '2.28.0';
+exports.SDK_VERSION = '2.28.2';

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@myapihq/sdk",
   "license": "Apache-2.0",
-  "version": "2.28.0",
+  "version": "2.28.2",
   "description": "TypeScript SDK for the MyAPI ecosystem",
   "repository": {
     "type": "git",