t
tfiwm
10/27/2018, 10:08 AMn
nilan
10/27/2018, 11:04 AMare you using Prisma Cloud?
nilan
10/27/2018, 11:04 AMdon't know why you're message looks so weird, but this is an issue about your authentication token (CLI authenticates against Prisma Cloud or against Prisma Server)
t
tfiwm
10/27/2018, 11:05 AMi am deploying it to now
tfiwm
10/27/2018, 11:06 AMit worked really well but from one day to another i was not able to deploy changes to the prisma server …
tfiwm
10/27/2018, 11:06 AMto the production server i can deploy and to the local too
n
nilan
10/27/2018, 11:09 AMdid you change the management api secret?
t
tfiwm
10/27/2018, 11:09 AMnope
tfiwm
10/27/2018, 11:09 AMi even deleted the prisma databases and the server
tfiwm
10/27/2018, 11:10 AMcreated new management api key
n
nilan
10/27/2018, 11:10 AMuh
t
tfiwm
10/27/2018, 11:10 AMand deployed the new one
tfiwm
10/27/2018, 11:10 AMstill same issue
n
nilan
10/27/2018, 11:10 AMwhat's the shape of ~/.prisma/config.yml?Please don't share any values, just the shape.
t
tfiwm
10/27/2018, 11:12 AM😉 the backend serve says this now
java.lang.RuntimeException: ProjectHelper: Could not resolve project with id: visual-knight@test
tfiwm
10/27/2018, 11:12 AMhe should create new one after deleted everything right?
n
nilan
10/27/2018, 11:12 AMI don't understand your question
t
tfiwm
10/27/2018, 11:13 AMprisma server sorry
n
nilan
10/27/2018, 11:13 AMsounds like your fiddling around with stuff and things got inconsistent somehow
t
tfiwm
10/27/2018, 11:15 AMbut after everything was deleted?
tfiwm
10/27/2018, 11:15 AMshould be a greenfield
tfiwm
10/27/2018, 11:15 AMi can do it again 😄
n
nilan
10/27/2018, 11:16 AMdepends on how you deleted everything, how you're persisting stuff etc
nilan
10/27/2018, 11:16 AM"deleting everything" can mean a lot of different things
t
tfiwm
10/27/2018, 11:16 AMits a docker now deplyoment which i delete so the prisma server should be deleted
n
nilan
10/27/2018, 11:16 AMOk then
t
tfiwm
10/27/2018, 11:16 AMand databases are just 2 prisma and the deployed one
tfiwm
10/27/2018, 11:16 AMor do i miss something?
n
nilan
10/27/2018, 11:17 AMwhat I can say is that the original error is likely caused by a syntax error in your config file or some other issue related to your authentication token
t
tfiwm
10/27/2018, 11:18 AMprisma deploy just talks to the prisma server with the management secret right?
tfiwm
10/27/2018, 11:19 AM Copy code
managementApiSecret: PRISMA_MANAGEMENT_API_SECRET
port: 4466
databases:
default:
connector: mysql
port: 3306
host: SQL_HOST
user: SQL_USER
password: SQL_PASSWORD
migrations: true
database: prisma
schema: privatetfiwm
10/27/2018, 11:19 AMi have the same setup for prod and test stage
tfiwm
10/27/2018, 11:22 AMwhere was the place where i have to put the management secret inside the configs?
tfiwm
10/27/2018, 11:22 AMjust to be sure
tfiwm
10/27/2018, 11:31 AMhmm there is no entry in the table CloudSecret after deployment…i think there should one entry with the management secret right?
2 Views