-
Notifications
You must be signed in to change notification settings - Fork 361
ClientContext, CognitoIdentity are not initialized #249
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I suggest we use an extra field in Context to capture any additional fields of headers AWS may send our way. The change them faster than we update our structutes. |
Sample output for Context from inside the handler:
|
@bahildebrand Blake, I lost track of it, but a quick look at the master branch tells me it's not really finished. I stand to be corrected, though. lambda-runtime
lambda-http
From what I remember, I put the structs in, copied their descriptions from AWS docs and left it at that because I was not using Cognito at the time and had no easy way of testing. That's what was merged. The project I'm working on will need this feature at some point. I'm happy to complete this issue as soon as I get to that. |
If I recall correctly, the CognitoIdentity and ClientContext values are only filled by early iterations of the mobile SDKs that directly invoked a Lambda function. This pattern is now discouraged and we now suggest that customers invoke Lambda functions through an API Gateway or an ALB. While we can fill in these values, I think that In your use-case, can you avoid using these fields/invoking Lambda functions directly? |
Neither
pub client_context: Option<ClientContext>
norpub identity: Option<CognitoIdentity>
from Context structure are ever set to any value.They are declared, but are never used.
Relates to PR #248
The text was updated successfully, but these errors were encountered: