sarahlazarich
commented
4 months ago YL: Pretty Easy, take the same format as the old one and just run it. Can use the script runner once that's done? CB: Why would this use the script runner if we aren't using this repeatedly? YL: It's kinda not meant for this, but you can always make a new endpoint for each AMI chart. Makes more sense to love here then anywhere else? End state will be a UI. CB: Was picturing something stand alone just building migrations like in TypeORM YL: In Prisma, you don't get a typescript file like in type orm, would have to write a query. In future, want to only have data changes through a script runner (instead of migrations) bc you have access to nestjs. EJ: Before we have this surfaced in the UI do we need to be connected right to prod to do this? YL: This is an endpoint not protected by passkey - script runner is baked into the API
The script we have historically used to update AMI charts is built for our old backend. We will need to replicate that for Prisma.