Hello :wave: hoping to get a comment from the Pul...
# automation-api
Hello 👋 hoping to get a comment from the Pulumi team on this one... I've just started seeing this error pop up out of nowhere (pretty sure I've not changed the code at all since I last ran it)
Copy code
  const error = new Error(message);
Error: 14 UNAVAILABLE: No connection established
    at callErrorFromStatus (/Users/REDACTED/code/infrastructure/node_modules/@grpc/grpc-js/src/call.ts:81:17)
    at Object.onReceiveStatus (/Users/REDACTED/code/infrastructure/node_modules/@grpc/grpc-js/src/client.ts:356:55)
    at Object.onReceiveStatus (/Users/REDACTED/code/infrastructure/node_modules/@grpc/grpc-js/src/client-interceptors.ts:455:34)
    at Object.onReceiveStatus (/Users/REDACTED/code/infrastructure/node_modules/@grpc/grpc-js/src/client-interceptors.ts:417:48)
    at /Users/REDACTED/code/infrastructure/node_modules/@grpc/grpc-js/src/resolving-call.ts:111:24
    at processTicksAndRejections (node:internal/process/task_queues:78:11)
for call at
    at ServiceClientImpl.makeUnaryRequest (/Users/REDACTED/code/infrastructure/node_modules/@grpc/grpc-js/src/client.ts:326:30)
    at ServiceClientImpl.registerResourceOutputs (/Users/REDACTED/code/infrastructure/node_modules/@grpc/grpc-js/src/make-client.ts:189:15)
    at /Users/REDACTED/code/infrastructure/node_modules/@pulumi/runtime/resource.ts:971:42
    at new Promise (<anonymous>)
    at Object.<anonymous> (/Users/REDACTED/code/infrastructure/node_modules/@pulumi/runtime/resource.ts:970:21)
    at Generator.next (<anonymous>)
    at fulfilled (/Users/REDACTED/code/infrastructure/node_modules/@pulumi/pulumi/runtime/resource.js:18:58)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
error Command failed with exit code 1.
@wonderful-motorcycle-58005 do you have security software on your machine that might block outbound connections? pulumi connects to resource providers over GRPC on localhost, sometimes software can block these
I haven't changed any config that Im aware of in the past week or two since I last ran the automation api script
I've found the source of the issue, I had forgot to sso login and specify my AWS_PROFILE before running the command to invoke the automation API This is an awful error message for a situation where it simply can't find/authenticate with my AWS credentials. I will open a GitHub issue reporting this
@wonderful-motorcycle-58005 agreed that he failure mode and error messages here should be substantially better. Would you mind opening an issue? github.com/pulumi/pulumi/issues/new
Looks like this is the exact issue you hit, already an open issue: https://github.com/pulumi/pulumi/issues/12970 And luckily there is a PR open with a fix! https://github.com/pulumi/pulumi/pull/13070