Support Lambda-Extension-Accept-Feature for extension registration

[mwudtke]

When calling the register API during extension initialization, there is an optional request header called Lambda-Extension-Accept-Feature that allows you to get the account ID associated with the Lambda function on the response body from the register API call documentation reference. The lambda-extension crate, however, has no way for consumers to add this header to the request, or to receive the accountId 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?

[calavera]

Feel free to open a PR to support it. We'll appreciate the help.

[calavera]

I've implemented this in #887

[github-actions]

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.