I know why is failing, I am behind a proxy/firewal...
# randomm
Michael H.
07/19/2018, 10:18 PMI know why is failing, I am behind a proxy/firewall, but I wonder why on every command, this prisma cli is trying to call the cloud?
j
Jenkins
07/20/2018, 6:40 AMWhat is the endpoint in your prisma.yml?
m
Michael H.
07/20/2018, 6:47 PMit is a local docker image
Michael H.
07/20/2018, 6:48 PMPRISMA_ENDPOINT=“http://localhost:4466/gl-clinic/dev”
j
Jenkins
07/21/2018, 6:14 PMSo in your prisma.yml file you have the following:
Copy code
...
endpoint: <http://localhost:4466/gl-clinic/dev>
...d
divyendu
07/23/2018, 2:50 AMYou should be able to using Prisma behind a proxy. This is not documented yet but you can do something like
Copy code
$ npm install -g proxy
$ DEBUG="*" proxy -p 8080
$ HTTP_PROXY=<http://localhost:8080> HTTPS_PROXY=<https://localhost:8080> prisma deploy👍 1
j
Jenkins
07/23/2018, 6:09 AMDid not know you could do that! Learned something as well!
👍 1
d
divyendu
07/23/2018, 6:31 AMNote that this doesn't work with all CLI tools. Prisma implements that here:
https://github.com/prismagraphql/prisma/blob/da604b77eac81455ace4a1f665248877aa968215/cli/packages/prisma-yml/src/utils/getProxyAgent.ts
m
Michael H.
07/23/2018, 3:59 PMHi @Jenkins and @divyendu thanks for the comments.
j
Jenkins
07/23/2018, 4:00 PMDe nada! Happy to 'help' in this case 🙂
m
Michael H.
07/23/2018, 4:01 PMThe CLI commands seem to be working behind a proxy, It does show the error and it looks weird but it seems to be deploying the changes
Michael H.
07/23/2018, 4:02 PMI just have the question of: if I am working locally only - on a docker setup - why is the command trying to call the cloud “api.cloud.prisma.sh”
Michael H.
07/23/2018, 4:02 PMI asked for 2 reasons, #1 is Security, I want to make sure there is no info trying to go out
Michael H.
07/23/2018, 4:03 PMand #2 is I am hoping to talk to the architects to possible try to implement graphql and this prisma tooling seems like and awesome way to go about it
Michael H.
07/23/2018, 4:03 PMGracias! for your time
Michael H.
07/25/2018, 5:13 PM@Jenkins yes that is what I have in my prisma.yml file, that is why I don’t understand why it seems the cli is trying to call “api.clould.prisma.sh”, when running behind a proxy, the deploy command works - deploying to local docker - but I see the error of this other call being blocked., what thoes the cli do with “api.cloud.prisma.sh”?
d
divyendu
07/26/2018, 5:36 AMI think that the CLI just checks if you are logged in or not.. because certain other code paths need it.
divyendu
07/26/2018, 5:36 AMThis might still be a residue from before, as making it offline was added as a feature later.
divyendu
07/26/2018, 5:37 AMIn later versions of CLI this error should not be there. Which Prisma CLI version do you use?
m
Michael H.
07/30/2018, 9:06 PMHi @divyendu I am using version 1.8.3
Michael H.
07/30/2018, 9:06 PMyour comments gives me comfort, thank you, for security reasons having it be offline seems like something awesome
Michael H.
07/30/2018, 9:07 PMsince I am working on a project I dont want to update the version to often to avoid some breaking change.
Michael H.
07/30/2018, 9:10 PMIf I am not mistaken, version 1.9.0 should have the this change in
Michael H.
07/30/2018, 9:10 PM3fca651 fix offline endpoint handling. Closes #865
Michael H.
07/30/2018, 9:12 PMI dont see any breaking change so I will upgrade, thanks for the help @divyendu this is an awesome tool
🙌 1
d
divyendu
07/30/2018, 9:20 PMAlso, generally, the app still sends some basic stuff, but if you are concerned about security, feel free to block the prisma endpoint on the machine by pointing it to 127.0.0.1 - also, feel free to create a new issue for a feature where Prisma CLI does not talk to cloud API at all 🙂
👍 1
m
Michael H.
07/31/2018, 5:26 PM👍
5 Views