@customyai/provisioning

Identity provisioning for TEST users in Customy Access, with an Access API key of one environment. Sobre @customyai/core.

npm install @customyai/provisioning @customyai/core

import { createProvisioning } from "@customyai/provisioning";

const provisioning = createProvisioning({
  environment: "staging", // required, no default: the key belongs to ONE environment
  baseUrl: process.env.CUSTOMY_ACCESS_URL!,
  clientId: process.env.CUSTOMY_CLIENT_ID!,
  clientSecret: process.env.CUSTOMY_CLIENT_SECRET!,
});

const { users } = await provisioning.testUsers.batch({ count: 3, emailDomain: "qa.example.com", reason: "e2e checkout run" });
await provisioning.users.upsert("qa-ana", { email: "[email protected]", password: "generate", reason: "manual QA account" });
await provisioning.testUsers.cleanup({ mine: true }, { reason: "end of QA session" });

• Auth: client-credentials JWT (audience customy-provisioning), cached in memory and renewed about 60 s before it expires. Customy-Environment travels on every request; a mismatch is CustomyEnvironmentMismatchError.
• Writes: each logical call gets an Idempotency-Key (override with idempotencyKey), reused on every retry. Retries happen only on 429 (honours Retry-After), 5xx, network failures and IDEMPOTENCY_IN_PROGRESS, with exponential backoff and full jitter (retry: { maxAttempts }, default 3). Never on other 4xx.
• Errors: CustomyProvisioningError (code, status, requestId, details) and subclasses CustomyScopeError (.scope), CustomyEnvironmentMismatchError, CustomyAuthError, CustomyConflictError (.currentVersion), CustomyRateLimitError (.retryAfter), CustomyCapabilityDisabledError, CustomyValidationError.
• Secrets: the client secret, bearer tokens, credentials.password and signin link are scrubbed from error messages, toJSON, util.inspect and the onRequest / onResponse hooks. Generated passwords and links are returned once; an idempotent replay returns null with redacted: true.
• Edge-ready: global fetch only, no Node imports.

Tests: withEphemeralUsers

import { withEphemeralUsers } from "@customyai/provisioning/testing"; // also @customyai/sdk/testing

await withEphemeralUsers({ count: 2, client: provisioning, emailDomain: "qa.example.com" }, async ([buyer]) => {
  await signIn(buyer.email, buyer.password);
}); // the batch is deleted in `finally`, even if the callback throws

ephemeralUsersFixture(options) gives setup() / teardown() for any runner's beforeAll / afterAll.