You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
or can take a more opinionated approach and make that happen as part of the pattern, but I have not seen setting ENV variables in any other construct. Open to suggestions.
This is 🐛 Bug Report
The text was updated successfully, but these errors were encountered:
This is actually a deficiency in the docs for that construct. aws-iot-lambda-dynamodb instantiates an aws-lambda-dynamodb construct internally - the docs for that construct confirm that an environment variable is set for the Lambda function: DDB_TABLE_NAME. It is a convention that when an environment variable is being set, we expose an optional property so clients can customize that name (e.g. - if a Lambda function is associated with 2 DDB tables), so in addition to updating the docs to show that an environment variable is getting set we'll also add the ability to customize the environment variable name to this interface similarly to what you see on aws-lambda-dynamodb.
Thanks for the heads up - we'll leave this issue open for the time being to remind to get this done.
Reproduction Steps
N/A
Error Log
N/A
Environment
N/A
Other
https://aws.amazon.com/blogs/aws/aws-solutions-constructs-a-library-of-architecture-patterns-for-the-aws-cdk/
shows how to link a dynamo table table
I can add this to the example
`iotToLambdaToDynamo.lambda_function.add_environment("TABLE_NAME", iotToLambdaToDymamo.dynamo_table.table_name)
or can take a more opinionated approach and make that happen as part of the pattern, but I have not seen setting ENV variables in any other construct. Open to suggestions.
This is 🐛 Bug Report
The text was updated successfully, but these errors were encountered: