async-lambda-unstable 0.6.15__tar.gz → 0.6.16__tar.gz

async_lambda_unstable-0.6.15/README.md → async_lambda_unstable-0.6.16/PKG-INFO

@@ -1,3 +1,15 @@
+Metadata-Version: 2.5
+Name: async-lambda-unstable
+Version: 0.6.16
+Summary: A framework for creating AWS Lambda Async Workflows. - Unstable Branch
+Author-email: "Nuclei, Inc" <engineering@nuclei.ai>
+Requires-Dist: click>=8.0.0
+Requires-Dist: typing-extensions>=4.0.0
+Provides-Extra: local
+Requires-Dist: boto3; extra == 'local'
+Requires-Dist: flask<3.0.0,>=2.3.0; extra == 'local'
+Description-Content-Type: text/markdown
+
 # async-lambda
 
 Async-lambda is a Python framework for building scalable, event-driven AWS Lambda applications with first-class support for asynchronous invocation via SQS queues. It provides a high-level abstraction for orchestrating Lambda functions, managing event triggers, and handling complex workflows with minimal boilerplate.
@@ -260,8 +272,14 @@ type, so adding or removing `image_uri` replaces each function, and CloudFormati
 function under the same custom name. The suffix lets the new function be created before the old one is
 deleted, so switching needs no manual deletion or downtime. Queue and schedule names are unchanged.
 
-Lambda layers and SnapStart are not supported on container images, so `layers` and `snap_start`
-raise an error at build time when `image_uri` is set.
+Lambda layers are not supported on container images, so `layers` raises an error at build time when
+`image_uri` is set. SnapStart (`snap_start=True`) is supported on container images that use an AWS
+base image for Python 3.12+, Java 11+, or .NET 8+.
+
+SnapStart only applies to published versions, never `$LATEST`. A task with `snap_start=True` sets
+`AutoPublishAlias: live` and `AutoPublishAliasAllProperties: true`, so each deploy that changes any
+function property (such as `Timeout` or `EphemeralStorage`) publishes a version. SAM points the task's event sources
+(API Gateway, SQS, schedules) at the `live` alias. This works for ZIP and image functions.
 
 ### subnet_ids
 

async_lambda_unstable-0.6.15/PKG-INFO → async_lambda_unstable-0.6.16/README.md

@@ -1,15 +1,3 @@
-Metadata-Version: 2.5
-Name: async-lambda-unstable
-Version: 0.6.15
-Summary: A framework for creating AWS Lambda Async Workflows. - Unstable Branch
-Author-email: "Nuclei, Inc" <engineering@nuclei.ai>
-Requires-Dist: click>=8.0.0
-Requires-Dist: typing-extensions>=4.0.0
-Provides-Extra: local
-Requires-Dist: boto3; extra == 'local'
-Requires-Dist: flask<3.0.0,>=2.3.0; extra == 'local'
-Description-Content-Type: text/markdown
-
 # async-lambda
 
 Async-lambda is a Python framework for building scalable, event-driven AWS Lambda applications with first-class support for asynchronous invocation via SQS queues. It provides a high-level abstraction for orchestrating Lambda functions, managing event triggers, and handling complex workflows with minimal boilerplate.
@@ -272,8 +260,14 @@ type, so adding or removing `image_uri` replaces each function, and CloudFormati
 function under the same custom name. The suffix lets the new function be created before the old one is
 deleted, so switching needs no manual deletion or downtime. Queue and schedule names are unchanged.
 
-Lambda layers and SnapStart are not supported on container images, so `layers` and `snap_start`
-raise an error at build time when `image_uri` is set.
+Lambda layers are not supported on container images, so `layers` raises an error at build time when
+`image_uri` is set. SnapStart (`snap_start=True`) is supported on container images that use an AWS
+base image for Python 3.12+, Java 11+, or .NET 8+.
+
+SnapStart only applies to published versions, never `$LATEST`. A task with `snap_start=True` sets
+`AutoPublishAlias: live` and `AutoPublishAliasAllProperties: true`, so each deploy that changes any
+function property (such as `Timeout` or `EphemeralStorage`) publishes a version. SAM points the task's event sources
+(API Gateway, SQS, schedules) at the `live` alias. This works for ZIP and image functions.
 
 ### subnet_ids
 

{async_lambda_unstable-0.6.15 → async_lambda_unstable-0.6.16}/async_lambda/__init__.py

@@ -22,4 +22,4 @@ from .models.events.managed_sqs_event import ManagedSQSEvent as ManagedSQSEvent
 from .models.events.scheduled_event import ScheduledEvent as ScheduledEvent
 from .models.events.unmanaged_sqs_event import UnmanagedSQSEvent as UnmanagedSQSEvent
 
-__version__ = "0.6.15"
+__version__ = "0.6.16"

{async_lambda_unstable-0.6.15 → async_lambda_unstable-0.6.16}/async_lambda/controller.py

@@ -624,12 +624,6 @@ class AsyncLambdaController:
             raise Exception(
                 "Lambda layers cannot be used with container images (image_uri is set)."
             )
-        if build_config.image_uri is not None and any(
-            task.snap_start for task in self.tasks.values()
-        ):
-            raise Exception(
-                "SnapStart cannot be used with container images (image_uri is set)."
-            )
         # SAM Globals does not accept PackageType or ImageConfig, so image functions
         # carry their package properties individually (see AsyncLambdaTask.get_sam_template).
         package_properties = (

{async_lambda_unstable-0.6.15 → async_lambda_unstable-0.6.16}/async_lambda/models/task.py

@@ -684,6 +684,12 @@ class AsyncLambdaTask(Generic[EventType, RT]):
             template[self.get_function_logical_id()]["Properties"]["SnapStart"] = {
                 "ApplyOn": "PublishedVersions"
             }
+            template[self.get_function_logical_id()]["Properties"][
+                "AutoPublishAlias"
+            ] = "live"
+            template[self.get_function_logical_id()]["Properties"][
+                "AutoPublishAliasAllProperties"
+            ] = True
 
         if self.trigger_type in MANAGED_SQS_TASK_TYPES:
             dlq_task = self.get_dlq_task()