-
Notifications
You must be signed in to change notification settings - Fork 248
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
docs(examples): update aws lambda tooling and iam role names #1224
Changes from all commits
0340136
b532892
9948383
e19e339
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -4,7 +4,7 @@ function_name: bolt_py_function | |
handler: aws_lambda.handler | ||
description: My first lambda function | ||
runtime: python3.8 | ||
# role: lambda_basic_execution | ||
role: bolt_python_lambda_invocation | ||
|
||
# S3 upload requires appropriate role with s3:PutObject permission | ||
# (ex. basic_s3_upload), a destination bucket, and the key prefix | ||
|
@@ -20,12 +20,11 @@ aws_secret_access_key: | |
# timeout: 15 | ||
# memory_size: 512 | ||
# concurrency: 500 | ||
# | ||
|
||
# Experimental Environment variables | ||
# Lambda environment variables | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. From what I can tell, these are no longer an experimental feature! 🎉 https://github.com/nficano/python-lambda?tab=readme-ov-file#environment-variables |
||
environment_variables: | ||
SLACK_BOT_TOKEN: ${SLACK_BOT_TOKEN} | ||
SLACK_SIGNING_SECRET: ${SLACK_SIGNING_SECRET} | ||
SLACK_BOT_TOKEN: ${SLACK_BOT_TOKEN} | ||
SLACK_SIGNING_SECRET: ${SLACK_SIGNING_SECRET} | ||
|
||
# If `tags` is uncommented then tags will be set at creation or update | ||
# time. During an update all other tags will be removed except the tags | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,6 +1,6 @@ | ||
#!/bin/bash | ||
rm -rf vendor && mkdir -p vendor/slack_bolt && cp -pr ../../slack_bolt/* vendor/slack_bolt/ | ||
pip install python-lambda -U | ||
pip install git+https://github.com/nficano/python-lambda | ||
lambda deploy \ | ||
--config-file aws_lambda_config.yaml \ | ||
--requirements requirements.txt | ||
--requirements requirements.txt |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,6 +1,6 @@ | ||
#!/bin/bash | ||
rm -rf slack_bolt && mkdir slack_bolt && cp -pr ../../slack_bolt/* slack_bolt/ | ||
pip install python-lambda -U | ||
pip install git+https://github.com/nficano/python-lambda | ||
lambda deploy \ | ||
--config-file lazy_aws_lambda_config.yaml \ | ||
--requirements requirements.txt |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,6 +1,6 @@ | ||
#!/bin/bash | ||
rm -rf slack_bolt && mkdir slack_bolt && cp -pr ../../slack_bolt/* slack_bolt/ | ||
pip install python-lambda -U | ||
pip install git+https://github.com/nficano/python-lambda | ||
lambda deploy \ | ||
--config-file aws_lambda_oauth_config.yaml \ | ||
--requirements requirements_oauth.txt |
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -4,9 +4,7 @@ function_name: bolt_py_function | |
handler: lazy_aws_lambda.handler | ||
description: My first lambda function | ||
runtime: python3.8 | ||
# role: lambda_basic_execution | ||
# Have lambda:InvokeFunction & lambda:GetFunction in the allowed actions | ||
Comment on lines
-7
to
-8
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The required roles are noted in the There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. yeah, makes sense! |
||
role: bolt_python_lambda_invocation | ||
role: bolt_python_lambda_invocation | ||
|
||
# S3 upload requires appropriate role with s3:PutObject permission | ||
# (ex. basic_s3_upload), a destination bucket, and the key prefix | ||
|
@@ -22,12 +20,11 @@ aws_secret_access_key: | |
# timeout: 15 | ||
# memory_size: 512 | ||
# concurrency: 500 | ||
# | ||
|
||
# Experimental Environment variables | ||
# Lambda environment variables | ||
environment_variables: | ||
SLACK_BOT_TOKEN: ${SLACK_BOT_TOKEN} | ||
SLACK_SIGNING_SECRET: ${SLACK_SIGNING_SECRET} | ||
SLACK_BOT_TOKEN: ${SLACK_BOT_TOKEN} | ||
SLACK_SIGNING_SECRET: ${SLACK_SIGNING_SECRET} | ||
|
||
# If `tags` is uncommented then tags will be set at creation or update | ||
# time. During an update all other tags will be removed except the tags | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@zimeg quick question: our internal report mentioned the necessity to rename this file. when you did testing for this change, was it unnecessary?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@seratch Thanks for checking on this! I noticed that updating the
role
used bydeploy.sh
was enough to resolve errors, but I will check this once more 🔍 ✨