Add workspace scoping to pipeline progress and expose findManyPipelineeProgress on graphql (#292)

Add workspace scoping to pipeline progress and expose findManyPipelineProgress on graphql
This commit is contained in:
Charles Bochet
2023-06-14 17:05:15 +02:00
committed by GitHub
parent 31f3950439
commit 5381e28253
104 changed files with 1393 additions and 98 deletions

View File

@ -0,0 +1,13 @@
/*
Warnings:
- You are about to drop the column `associableId` on the `pipeline_progresses` table. All the data in the column will be lost.
- You are about to drop the column `associableType` on the `pipeline_progresses` table. All the data in the column will be lost.
- Added the required column `progressableId` to the `pipeline_progresses` table without a default value. This is not possible if the table is not empty.
- Added the required column `progressableType` to the `pipeline_progresses` table without a default value. This is not possible if the table is not empty.
*/
-- AlterTable
ALTER TABLE "pipeline_progresses" RENAME "associableId" TO "progressableId";
ALTER TABLE "pipeline_progresses" RENAME "associableType" TO "progressableType";

View File

@ -0,0 +1,11 @@
/*
Warnings:
- Added the required column `workspaceId` to the `pipeline_progresses` table without a default value. This is not possible if the table is not empty.
*/
-- AlterTable
ALTER TABLE "pipeline_progresses" ADD COLUMN "workspaceId" TEXT NOT NULL;
-- AddForeignKey
ALTER TABLE "pipeline_progresses" ADD CONSTRAINT "pipeline_progresses_workspaceId_fkey" FOREIGN KEY ("workspaceId") REFERENCES "workspaces"("id") ON DELETE RESTRICT ON UPDATE CASCADE;