search

Graphcool / graphcool-framework

Apache License 2.0
1.77k stars 131 forks source link

Graphcool framework - Deploy not working #563

Open pbandjs opened 5 years ago

pbandjs commented 5 years ago

I have a graphcool framework project hosted on shared-ap-northeast-1 which I have updated many times over the past few months. Over the last week, i have tried changing permissions as well as adding new types but neither is reflected in my project. When i run graphcool deploy, with debug, the deployment terminates with:

...a bunch of stuff omitted for brevity...

client choosing clusterEndpoint https://api.graph.cool/system +45ms client Sending query +2ms client mutation($projectId: String!, $force: Boolean, $isDryRun: Boolean!, $config: String!) { client push(input: { client projectId: $projectId client force: $force client isDryRun: $isDryRun client config: $config client version: 1 client }) { client migrationMessages { client type client action client name client description client subDescriptions { client type client action client name client description client } client } client errors { client description client type client field client } client project { client id client name client alias client projectDefinitionWithFileContent client } client } client }

...a bunch of stuff omitted for brevity...

util timed out +0ms Exiting with code: 0

pbandjs commented 5 years ago

This still does not work for me. I need to launch this service this week. Anybody got any suggestions to fix this?

vitorpiovezam commented 5 years ago

same here, after choose the cluster to deploy, nothing happens

jinshin1013 commented 5 years ago

Here are some error stack when trying to deploy and authorize the cli

Failed to load resource: the server responded with a status of 502 ()
Access to fetch at 'https://cli-auth-api.graph.cool/prod/update' from origin 'https://console.graph.cool' 
has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the 
requested resource.
noobling commented 5 years ago

For me I found out I had a service already name the same as the one I am trying to deploy you need a different service name. Its a shame they have stopped supporting this, I know this is free and all but its not hard to let everyone that they are no longer maintaining it..

bre7 commented 5 years ago

For me I found out I had a service already name the same as the one I am trying to deploy you need a different service name. Its a shame they have stopped supporting this, I know this is free and all but its not hard to let everyone that they are no longer maintaining it..

Even for paying users support is pretty much dead 🤷‍♂️