You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've got the same issue as previously reported here.
{
"level": "WARN",
"message": "Ignoring error: HttpError: A JSON web token could not be decoded - https://docs.github.com/rest",
"sampling_rate": 0,
"service": "runners-scale-up",
"timestamp": "2025-02-19T02:05:17.258Z",
"xray_trace_id": "",
"region": "ap-southeast-2",
"environment": "cicd-linux-x64-ubuntu",
"aws-request-id": "",
"function-name": "cicd-linux-x64-ubuntu-scale-up",
"module": "lambda.ts"
}
I'm using the multi-runner module (latest version), and this is what I've done so far:
Got the module deployed + Github App (organization level)
Added the Webhook + secret (secret taken from SSM Parameter, couldn't find it in the output)
installed the app organization side with workflow-job subscription to events
Troubleshooting / what I've tried:
Can see the new events on GH Apps page coming in
In the /aws/lambda/cicd-webhook logs, I can see the webhook is working
sending message to SQS: {\"QueueUrl\":\"https://sqs.ap-southeast-2.amazonaws.com/XXXXXXXX/cicd-linux-x64-ubuntu-queued-builds
"message": "Successfully dispatched job for ploreco/PageBuilder to the queue https://sqs.ap-southeast-2.amazonaws.com/XXXXXXXX/cicd-linux-x64-ubuntu-queued-builds"
The output of cat app.private-key.pem | base64 is provided to the module like this:
Hey,
I've got the same issue as previously reported here.
I'm using the
multi-runner
module (latest version), and this is what I've done so far:workflow-job
subscription to eventsTroubleshooting / what I've tried:
/aws/lambda/cicd-webhook
logs, I can see the webhook is workingcat app.private-key.pem | base64
is provided to the module like this:github_app.key_base64
is a variable that is being used as a string (for now, hopefully #4420 is implemented :))I'll continue to troubleshoot on my side and update this issue with further details.
Thanks!
The text was updated successfully, but these errors were encountered: