Hi All, We are trying to do a fresh deploy of pris...
# orm-help
r
Hi All, We are trying to do a fresh deploy of prisma1 in one of our new cloud region. ( our application is using Prisma1 thats why we have to stick with it). While trying to run
prisma deploy --force --no-seed
we are getting an error the complains about
cluster$default
Copy code
ERROR: Project not found: 'cluster$default'
24-Sep-2020 22:11:59	
24-Sep-2020 22:11:59	{
24-Sep-2020 22:11:59	  "errors": [
24-Sep-2020 22:11:59	    {
24-Sep-2020 22:11:59	      "message": "Project not found: 'cluster$default'",
24-Sep-2020 22:11:59	      "code": 3016,
24-Sep-2020 22:11:59	      "requestId": "local:ckfhqavwf0vkh0734eamd1bd0"
24-Sep-2020 22:11:59	    }
24-Sep-2020 22:11:59	  ],
24-Sep-2020 22:11:59	  "status": 200
24-Sep-2020 22:11:59	}
would be helpful if some guidance is provided on this. We are on Prisma 1.30.5
r
Hey @Rashmi Bidanta 👋 Could you explain a bit about your setup?
r
yeah sure
I have already installed a running Prisma1 setup which is connected to postgresDB
we are in process of deploying the schema using prisma deploy so it creates all the necessary tables in postgres database
we have bamboo deployment job that connects to Prisma server and then invokes
prisma deploy
@Ryan let me know if this helps
the script seems to work fine for one of our other instance where the database already has the necessary tables
r
I have already installed a running Prisma1 setup
How and where have you added this setup?
r
Prisma1 is running in kubernetes
Copy code
image:
        repository: prismagraphql/prisma-prod
        tag: 1.30.5
thats the image we are using
in prisma-config yaml do we have to enable
Copy code
enableManagementApi: false
this is set to false right now
I thought I would give it a shot with
Copy code
prisma deploy -d -n  -e ../.env
but seems to be not working
when I remove the -n it goes to prisma cloud
and we do not have a cloud account
we already have the datamodel and all we want is to push this datamodel into the database
r
@Rashmi Bidanta this needs to be enabled as you’re creating a new deployment.
Copy code
enableManagementApi: true
Also, the important thing to note here is that you can only have a single instance with
enableManagementApi
set to
true
in the cluster. The rest of those would need to to have
enableManagementApi
set to
false
.
r
okay
let me give it a shot
💯 1
@Ryan it still seems to be failing