Allow lazy function invocation to target version/alias

[angrychimp]

Currently lazy responses are only targeting the $LATEST version of a given AWS function. This prevents meaningful A/B testing if you're using function versions/aliases to compare code changes. Adjusting the invoke method to use the function ARN from the current execution allows downstream code parity.

This change adds a variable (invoked_function_arn) to the request context, then uses that value when invoking the sub-request.

Category

• slack_bolt.App and/or its core components
• slack_bolt.async_app.AsyncApp and/or its core components
• Adapters in slack_bolt.adapter
• Document pages under /docs
• Others

Requirements (place an x in each [ ])

Please read the Contributing guidelines and Code of Conduct before creating this issue or pull request. By submitting, you are agreeing to those rules.

• I've read and understood the Contributing Guidelines and have done my best effort to follow them.
• I've read and agree to the Code of Conduct.
• I've run ./scripts/install_all_and_run_tests.sh after making the changes.

[CLAassistant]

All committers have signed the CLA.

[seratch]

Thanks for improving this! LGTM

[seratch]

This should work. The lambda invocation API accepts any of function name, function ARN, and partial ARN. https://docs.aws.amazon.com/cli/latest/reference/lambda/invoke.html#options

[seratch]

@angrychimp The change looks great to me already but this change requires a small update in the unit test code. Could you update the test code to be consistent with your code change?

[angrychimp]

Not sure how I missed that, but thanks for pointing it out. I've added the updated test script to the PR. I'm getting a seg-fault running the "run_tests" script which I believe is just an issue with my environment, but while I figure that out let me know if it looks like there's anything else I'm missing.

@angrychimp The change looks great to me already but this change requires a small update in the unit test code. Could you update the test code to be consistent with your code change?

[codecov]

Codecov Report

Merging #679 (7629bd4) into main (208992c) will increase coverage by 0.00%.
The diff coverage is 100.00%.

❗ Current head 7629bd4 differs from pull request most recent head e756010. Consider uploading reports for the commit e756010 to get more accurate results

@@           Coverage Diff           @@
##             main     #679   +/-   ##
=======================================
  Coverage   92.05%   92.05%           
=======================================
  Files         172      172           
  Lines        5864     5865    +1     
=======================================
+ Hits         5398     5399    +1     
  Misses        466      466           

Impacted Files	Coverage Δ
...ck_bolt/adapter/aws_lambda/lazy_listener_runner.py	55.00% <ø> (ø)
slack_bolt/adapter/aws_lambda/handler.py	95.89% <100.00%> (+0.05%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 208992c...e756010. Read the comment docs.

[seratch]

@angrychimp

I'm getting a seg-fault running the "run_tests" script which I believe is just an issue with my environment

We are aware of this potential error that can rarely happen but this is it not related to your changes. Also, retrying the test execution should succeed.

The CI builds are now successful! Thanks a lot for your contribution 🎉