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
* Add `cache_from` option in the docker-build module ([#641](https://github.com/terraform-aws-modules/terraform-aws-lambda/issues/641)) ([55cdaa6](https://github.com/terraform-aws-modules/terraform-aws-lambda/commit/55cdaa68a63413f4ae5724c8b3a09a6b10d72f12))
* Allow temp dir for poetry docker builds ([#638](https://github.com/terraform-aws-modules/terraform-aws-lambda/issues/638)) ([65ffea2](https://github.com/terraform-aws-modules/terraform-aws-lambda/commit/65ffea2cfd99a27b6be3fc3e48482cf0fb821f2f))
* Radically redesign the build plan form ([#646](https://github.com/terraform-aws-modules/terraform-aws-lambda/issues/646)) ([32d8d06](https://github.com/terraform-aws-modules/terraform-aws-lambda/commit/32d8d060a660b0ec5702403da1b970118f62a314))
* Support lambda function `vpc_config.ipv6_allowed_for_dual_stack` and event source mapping `tags` ([#628](https://github.com/terraform-aws-modules/terraform-aws-lambda/issues/628)) ([2a602f9](https://github.com/terraform-aws-modules/terraform-aws-lambda/commit/2a602f9a4f76d11005d1dba56d9c966a87553f4e))
60
+
61
+
62
+
### Bug Fixes
63
+
64
+
* Update CI workflow versions to latest ([#631](https://github.com/terraform-aws-modules/terraform-aws-lambda/issues/631)) ([d06718f](https://github.com/terraform-aws-modules/terraform-aws-lambda/commit/d06718f605294f59a42ae6e3db70bfd7b9fa35f3))
* Support `aws_lambda_event_source_mapping.document_db_event_source_config` ([#626](https://github.com/terraform-aws-modules/terraform-aws-lambda/issues/626)) ([5d48199](https://github.com/terraform-aws-modules/terraform-aws-lambda/commit/5d481996ed6ef5ce784847b7e5bae1bae1ee8bfd))
* Add support for kafka event source config ([#617](https://github.com/terraform-aws-modules/terraform-aws-lambda/issues/617)) ([2c077cb](https://github.com/terraform-aws-modules/terraform-aws-lambda/commit/2c077cb1450af76cf44b56bfeba796ee9d9d9a00))
Copy file name to clipboardExpand all lines: README.md
+11-6Lines changed: 11 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,7 @@ This Terraform module is the part of [serverless.tf framework](https://github.co
16
16
## Features
17
17
18
18
- Build dependencies for your Lambda Function and Layer.
19
-
- Support builds locally and in Docker (with or without SSH agent support for private builds).
19
+
- Support builds locally and in Docker (with or without SSH agent support for private builds) for any runtime and architecture supported by AWS Lambda.
20
20
- Create deployment package or deploy existing (previously built package) from local, from S3, from URL, or from AWS ECR repository.
21
21
- Store deployment packages locally or in the S3 bucket.
22
22
- Support almost all features of Lambda resources (function, layer, alias, etc.)
@@ -384,7 +384,7 @@ When `source_path` is set to a list of directories the content of each will be t
384
384
385
385
### Combine various options for extreme flexibility
386
386
387
-
This is the most complete way of creating a deployment package from multiple sources with multiple dependencies. This example is showing some of the available options (see [examples/build-package](https://github.com/terraform-aws-modules/terraform-aws-lambda/tree/master/examples/build-package) for more):
387
+
This is the most complete way of creating a deployment package from multiple sources with multiple dependencies. This example is showing some of the available options (see [examples/build-package](https://github.com/terraform-aws-modules/terraform-aws-lambda/tree/master/examples/build-package)and [examples/runtimes](https://github.com/terraform-aws-modules/terraform-aws-lambda/tree/master/examples/runtimes)for more):
388
388
389
389
```hcl
390
390
source_path = [
@@ -643,6 +643,7 @@ Q4: What does this error mean - `"We currently do not support adding policies fo
643
643
-[Complete](https://github.com/terraform-aws-modules/terraform-aws-lambda/tree/master/examples/complete) - Create Lambda resources in various combinations with all supported features.
644
644
-[Container Image](https://github.com/terraform-aws-modules/terraform-aws-lambda/tree/master/examples/container-image) - Create a Docker image with a platform specified in the Dockerfile (using [docker provider](https://registry.terraform.io/providers/kreuzwerker/docker)), push it to AWS ECR, and create Lambda function from it.
645
645
-[Build and Package](https://github.com/terraform-aws-modules/terraform-aws-lambda/tree/master/examples/build-package) - Build and create deployment packages in various ways.
646
+
-[Runtimes](https://github.com/terraform-aws-modules/terraform-aws-lambda/tree/master/examples/build-package) - Build and create deployment packages for various runtimes (such as Rust, Go, Java).
646
647
-[Alias](https://github.com/terraform-aws-modules/terraform-aws-lambda/tree/master/examples/alias) - Create static and dynamic aliases in various ways.
647
648
-[Deploy](https://github.com/terraform-aws-modules/terraform-aws-lambda/tree/master/examples/deploy) - Complete end-to-end build/update/deploy process using AWS CodeDeploy.
648
649
-[Async Invocations](https://github.com/terraform-aws-modules/terraform-aws-lambda/tree/master/examples/async) - Create Lambda Function with async event configuration (with SQS, SNS, and EventBridge integration).
@@ -660,13 +661,13 @@ Q4: What does this error mean - `"We currently do not support adding policies fo
| <aname="input_image_config_working_directory"></a> [image\_config\_working\_directory](#input\_image\_config\_working\_directory)| The working directory for the docker image |`string`|`null`| no |
797
799
| <aname="input_image_uri"></a> [image\_uri](#input\_image\_uri)| The ECR image URI containing the function's deployment package. |`string`|`null`| no |
798
800
| <aname="input_invoke_mode"></a> [invoke\_mode](#input\_invoke\_mode)| Invoke mode of the Lambda Function URL. Valid values are BUFFERED (default) and RESPONSE\_STREAM. |`string`|`null`| no |
801
+
| <aname="input_ipv6_allowed_for_dual_stack"></a> [ipv6\_allowed\_for\_dual\_stack](#input\_ipv6\_allowed\_for\_dual\_stack)| Allows outbound IPv6 traffic on VPC functions that are connected to dual-stack subnets |`bool`|`null`| no |
799
802
| <aname="input_kms_key_arn"></a> [kms\_key\_arn](#input\_kms\_key\_arn)| The ARN of KMS key to use by your Lambda Function |`string`|`null`| no |
800
803
| <aname="input_lambda_at_edge"></a> [lambda\_at\_edge](#input\_lambda\_at\_edge)| Set this to true if using Lambda@Edge, to enable publishing, limit the timeout, and allow edgelambda.amazonaws.com to invoke the function |`bool`|`false`| no |
801
804
| <aname="input_lambda_at_edge_logs_all_regions"></a> [lambda\_at\_edge\_logs\_all\_regions](#input\_lambda\_at\_edge\_logs\_all\_regions)| Whether to specify a wildcard in IAM policy used by Lambda@Edge to allow logging in all regions |`bool`|`true`| no |
@@ -825,6 +828,7 @@ No modules.
825
828
| <aname="input_publish"></a> [publish](#input\_publish)| Whether to publish creation/change as new Lambda Function Version. |`bool`|`false`| no |
826
829
| <aname="input_putin_khuylo"></a> [putin\_khuylo](#input\_putin\_khuylo)| Do you agree that Putin doesn't respect Ukrainian sovereignty and territorial integrity? More info: https://en.wikipedia.org/wiki/Putin_khuylo!|`bool`|`true`| no |
827
830
| <aname="input_recreate_missing_package"></a> [recreate\_missing\_package](#input\_recreate\_missing\_package)| Whether to recreate missing Lambda package if it is missing locally or not |`bool`|`true`| no |
831
+
| <aname="input_recursive_loop"></a> [recursive\_loop](#input\_recursive\_loop)| Lambda function recursion configuration. Valid values are Allow or Terminate. |`string`|`null`| no |
828
832
| <aname="input_replace_security_groups_on_destroy"></a> [replace\_security\_groups\_on\_destroy](#input\_replace\_security\_groups\_on\_destroy)| (Optional) When true, all security groups defined in vpc\_security\_group\_ids will be replaced with the default security group after the function is destroyed. Set the replacement\_security\_group\_ids variable to use a custom list of security groups for replacement instead. |`bool`|`null`| no |
829
833
| <aname="input_replacement_security_group_ids"></a> [replacement\_security\_group\_ids](#input\_replacement\_security\_group\_ids)| (Optional) List of security group IDs to assign to orphaned Lambda function network interfaces upon destruction. replace\_security\_groups\_on\_destroy must be set to true to use this attribute. |`list(string)`|`null`| no |
830
834
| <aname="input_reserved_concurrent_executions"></a> [reserved\_concurrent\_executions](#input\_reserved\_concurrent\_executions)| The amount of reserved concurrent executions for this Lambda Function. A value of 0 disables Lambda Function from being triggered and -1 removes any concurrency limitations. Defaults to Unreserved Concurrency Limits -1. |`number`|`-1`| no |
@@ -866,6 +870,7 @@ No modules.
866
870
|------|-------------|
867
871
| <aname="output_lambda_cloudwatch_log_group_arn"></a> [lambda\_cloudwatch\_log\_group\_arn](#output\_lambda\_cloudwatch\_log\_group\_arn)| The ARN of the Cloudwatch Log Group |
868
872
| <aname="output_lambda_cloudwatch_log_group_name"></a> [lambda\_cloudwatch\_log\_group\_name](#output\_lambda\_cloudwatch\_log\_group\_name)| The name of the Cloudwatch Log Group |
873
+
| <aname="output_lambda_event_source_mapping_arn"></a> [lambda\_event\_source\_mapping\_arn](#output\_lambda\_event\_source\_mapping\_arn)| The event source mapping ARN |
869
874
| <aname="output_lambda_event_source_mapping_function_arn"></a> [lambda\_event\_source\_mapping\_function\_arn](#output\_lambda\_event\_source\_mapping\_function\_arn)| The the ARN of the Lambda function the event source mapping is sending events to |
870
875
| <aname="output_lambda_event_source_mapping_state"></a> [lambda\_event\_source\_mapping\_state](#output\_lambda\_event\_source\_mapping\_state)| The state of the event source mapping |
871
876
| <aname="output_lambda_event_source_mapping_state_transition_reason"></a> [lambda\_event\_source\_mapping\_state\_transition\_reason](#output\_lambda\_event\_source\_mapping\_state\_transition\_reason)| The reason the event source mapping is in its current state |
@@ -895,7 +900,7 @@ No modules.
895
900
| <aname="output_lambda_role_unique_id"></a> [lambda\_role\_unique\_id](#output\_lambda\_role\_unique\_id)| The unique id of the IAM role created for the Lambda Function |
896
901
| <aname="output_local_filename"></a> [local\_filename](#output\_local\_filename)| The filename of zip archive deployed (if deployment was from local) |
897
902
| <aname="output_s3_object"></a> [s3\_object](#output\_s3\_object)| The map with S3 object data of zip archive deployed (if deployment was from S3) |
0 commit comments