{#if existingWorkspace && chooseFolder}
Folder inside {existingWorkspace}

Everything the project ships is imported into this folder.

{#if folder.trim() && !folderValid}

Letters, digits, dashes and underscores only.

{/if}
{/if}

What this will do

{#if execution?.error} {execution.error} {/if} {#if showNotes} Resources are imported as empty stubs — set their values after import; one whose path is already in the workspace is left exactly as it is and reported as already there, so a value you have since filled in is never overwritten. Trigger kinds are recreated disabled, except GCP and Azure triggers, which manage cloud subscriptions at creation and must be re-created manually after filling their resource. Kafka, NATS, SQS, GCP and Azure triggers all require Enterprise. Triggers that reference a resource depend on stubs imported empty, so fill in the resource value before re-enabling the trigger. {/if}
{#if !execution?.done} {:else} {/if}
{#if execution?.createdWorkspace && !execution.done} {/if} {#if execution?.done} {#if execution.error} {/if} {:else} {/if}
closeMigrationReview(false)}> closeMigrationReview(false)}>
{reviewList.length === 1 ? 'This data table is' : 'These data tables are'} already set up{existingWorkspace ? ` in ${existingWorkspace}` : ''} and may already hold data. These migrations were written to create the project's tables, so running them here can alter or drop what is in them. Read the SQL before you run it, and skip anything you are unsure of.

Review and edit the SQL, then choose which to run. A migration runs against the data table of the same name in the destination workspace; if that data table has migrations enabled it is recorded, otherwise it runs once as a preview job.

{#each reviewList as m (m.datatable_name)}
{m.datatable_name}
{#if m.run} {/if}
{/each}
{#snippet actions()} {/snippet}