fix: add ACTIVE_CUSTOM_IMAGE_SETUP_STATUSES to environments service mocks

The constant was added as a named export in the environments service but
the vi.mock factories in environment-custom-image-routes and
environment-instance-routes tests did not include it, causing vitest to
throw on import.

Co-Authored-By: Paperclip <noreply@paperclip.ing>
This commit is contained in:
Harold KimandPaperclip committed 2026-07-09 09:38:58 +00:00
1 parent dfc4021093
commit b07c6ec689
2 files changed
+2

No files matched your search

@@ -70,6 +70,7 @@ vi.mock("../services/index.js", () => ({
vi.mock("../services/environments.js", () => ({
environmentService: () => mockEnvironmentService,
ACTIVE_CUSTOM_IMAGE_SETUP_STATUSES: ["starting", "waiting_for_user", "capturing"],
}));
vi.mock("../services/execution-workspaces.js", () => ({
@@ -60,6 +60,7 @@ vi.mock("../services/index.js", () => ({
vi.mock("../services/environments.js", () => ({
environmentService: () => mockEnvironmentService,
ACTIVE_CUSTOM_IMAGE_SETUP_STATUSES: ["starting", "waiting_for_user", "capturing"],
}));
vi.mock("../services/execution-workspaces.js", () => ({