Closed mwudtke closed 2 months ago
Feel free to open a PR to support it. We'll appreciate the help.
I've implemented this in #887
This issue is now closed. Comments on closed issues are hard for our team to see. If you need more assistance, please either tag a team member or open a new issue that references this one.
When calling the
register
API during extension initialization, there is an optional request header calledLambda-Extension-Accept-Feature
that allows you to get the account ID associated with the Lambda function on the response body from theregister
API call documentation reference. Thelambda-extension
crate, however, has no way for consumers to add this header to the request, or to receive theaccountId
on the response body.There should either be a way to opt-in to these "additional features" when registering extensions, or possibly even include the
accountId
by default.Has this been considered before? Is there a preference by the maintainers for including something like that by default vs making it a parameter?