Prisma

Anyone ever run into a situation where `prisma deploy` wants to deploy to prisma cloud (despite contents of `prisma.yml`) but every other command, including `prisma reset` appears to be working fine?

tried running `prisma deploy` from inside a docker container an could not get it to connect to the sibling prisma instance

Had `provider:<http://prisma:4466>` in `prisma.yml` and `prisma info` made sense but still tried to deploy to the cloud. 

I thought I was having trouble getting a lock on the db, but reset worked and dropping down to only one prisma instance failed to solve it. 

Dropped back a version or so (1.28) and it seems to have resolved. :man-shrugging:

know what, I was running 1.29-beta to try out the admin tool, think we have a winner there..

wanna have the honor of filing a bug report :slightly_smiling_face:

Same. :wink: but dropping down to 1.28.5 did not solve it. 

Not particularly. Lol. Let’s wait and see what the crew says tomorrow. 

Looks like a regression since 1.28.something&lt;=5 then.

btw. since you were trying to run `deploy` from within docker - why? I was doing it as a one-off to populate the DB with the correct schema, but I'm not really sure if that's how I'm supposed to do it.

I was telepresence-ing into a kubernetes cluster. 

you don't happen to know if there's a best practice for how to handle schema deployment/upgrades when in containers?

(other than _always_ running `deploy` before starting my app that is)

and that does _not_ sound like best practice...

Are you running deploy because you’re not stateful at all? 

nah, mostly as a CI/CD thing (or at least I'm thinking it could be used that way during dev)

Not sure I follow. :man-shrugging:

I don’t end up running deploy all that often in production.  

I was more thinking during development with something like gitlab where new environments get created/destroyed on branch creation/deletion

so I was looking at it as a Q&amp;D way to create/populate tables/data

<@UH2ABE7DM>: Can you please provide a small reproduction for which version is broken and maybe with a `prisma.yml`? I don't think that I have seen this issue before.

<https://github.com/prisma/prisma/issues/4215>