After creating a Prisma Server using the Heroku integration, renaming that Heroku app name (and thus the endpoint URL) in Heroku's settings dashboard makes the Prisma service and server unavailable. Prisma Cloud still shows the old endpoint URL, and there doesn't seem to be a way for me to adjust the endpoint URL in Prisma Cloud (assuming that would fix it).
Similarly, I started out on the Hobby Dev PostgreSQL database, but quickly ran out of space and followed Heroku's upgrade procedure to move the data to a new Hobby Basic plan. From Heroku's POV, everything worked correctly, but Prisma Cloud still says I'm on the old database version.
I'm a little concerned about using Prisma in production with the Prisma Cloud Heroku integration if there's no clean way for us to scale the database as app usage grows. Perhaps this problem wouldn't exist if I deployed Prisma myself using Docker?
After creating a Prisma Server using the Heroku integration, renaming that Heroku app name (and thus the endpoint URL) in Heroku's settings dashboard makes the Prisma service and server unavailable. Prisma Cloud still shows the old endpoint URL, and there doesn't seem to be a way for me to adjust the endpoint URL in Prisma Cloud (assuming that would fix it).
Similarly, I started out on the Hobby Dev PostgreSQL database, but quickly ran out of space and followed Heroku's upgrade procedure to move the data to a new Hobby Basic plan. From Heroku's POV, everything worked correctly, but Prisma Cloud still says I'm on the old database version.
I'm a little concerned about using Prisma in production with the Prisma Cloud Heroku integration if there's no clean way for us to scale the database as app usage grows. Perhaps this problem wouldn't exist if I deployed Prisma myself using Docker?