I upgraded a project to the “CLI”, I disabled the old authentication integration before doing so, then added the basic auth template to the project, and deployed to prod. When I go to the playground, I can login with a user I had previously created, but invoking the mutation “signupUser” from the playground always returns an “unexpected error” (5001), and I notice that the “requestId”: “eu-west-1simplecj9pkkz4spypu0102kzl4o1wg” doesn’t actually match mu project id

have a look at your .graphcoolrc default API ID

I have this in my .graphcoolrc

targets:
default: prod
prod: shared-eu-west-1/cj9aalofn1udi01323iwp3pjs

I've got

clusters:
  default: shared-eu-west-1
targets:
  default: dev
  dev: shared-eu-west-1/XXXXX

my .graphcoolrc was created by graph.cool when I upgraded the project to CLI

hmmm you might have to ask someone else as I've not used docker on graphcool

a request id is something different than a service id, so it shouldn't match 😉

here comes Nilan to the rescure 🙂

what's the output of

graphcool logs

for that function invocation?

*rescue

hi @nilan

you can use

graphcool logs -f signUp

in the CLI

thanks

you can add -tail I think