Oskar Otwinowski
4efe0a07c4
Members added by SSO just-in-time provisioning or Directory Sync never got their per-member DEVELOPMENT environments - only invite acceptance and project creation created them. `trigger dev` returned "Environment not found" for those members and the dashboard had no dev view. ensureOrgMember now queues provisioning for every membership it settles, so both paths are covered and members missing environments are repaired on their next sync. Provisioning runs as a common-worker job to keep sign-in and directory webhooks off the per-project write loop. A failed enqueue surfaces for Directory Sync, whose worker retries the idempotent effect, and is swallowed for sign-in, where the next login enqueues again. Environment creation now tolerates a concurrent creator so the project-creation loop and the job cannot collide on the unique index. Also fixes environment resolution ignoring dev-environment ownership: a member without their own dev environment could be handed a colleague's and have it persisted as their dashboard preference.
21 lines
680 B
TypeScript
21 lines
680 B
TypeScript
import { type RuntimeEnvironmentType } from "@trigger.dev/database";
|
|
|
|
type AccessibleEnvironmentInput = {
|
|
type: RuntimeEnvironmentType;
|
|
orgMember: { userId: string } | null;
|
|
};
|
|
|
|
/**
|
|
* The first environment the user may actually use. Development environments are
|
|
* per-member, so resolving one by slug or stored id alone can return another
|
|
* member's; every other type is shared by the project.
|
|
*/
|
|
export function selectAccessibleEnvironment<T extends AccessibleEnvironmentInput>(
|
|
environments: T[],
|
|
userId: string
|
|
): T | undefined {
|
|
return environments.find(
|
|
(environment) => environment.type !== "DEVELOPMENT" || environment.orgMember?.userId === userId
|
|
);
|
|
}
|