Reading the AWS Request ID about laravel-bridge HOT 9 OPEN

Yes:

from laravel-bridge.

Hmm, alright, I have to be more specific I guess: at this point I am not getting the X-Request-ID header in my requests.
I turned request_context on, but that doesn't give me any information about the AWS request.

I'm logging all headers coming in to my controller via the request, but it's not there.
Is there a way to get at the current context either in a controller, or middleware, or somewhere in that chain?

from laravel-bridge.

I am having the same problem. @harmenjanssen can you reopen the issue as ATM it's not clear how to use this config option :/

from laravel-bridge.

Does your request object not have the X-Request-ID header?

from laravel-bridge.

Does your request object not have the X-Request-ID header?

Nope, it does not.

from laravel-bridge.

Mhhh, turns out my apps aren't actually using this anymore. @georgeboot Do we have any way to access the AWS request id?

from laravel-bridge.

Afk atm, but there should be a $_SERVER var called HTTP_X_REQUEST_ID I believe

from laravel-bridge.

As @georgeboot said, I had a look into $_SERVER and found out that $_SERVER['LAMBDA_INVOCATION_CONTEXT'] has necessary info:

$requestId = null;
if (isset($_SERVER['LAMBDA_INVOCATION_CONTEXT'])) {
    $lambdaContext = json_decode($_SERVER['LAMBDA_INVOCATION_CONTEXT']);
    $requestId = $lambdaContext?->awsRequestId;
}

from laravel-bridge.

I feel like we should expose the invocation context a little better, maybe even attach some of the data to the Request object.

from laravel-bridge.