@lambda-kata/cdk 0.1.3-rc.80 → 0.1.3-rc.84

package/out/tsc/src/config-layer.d.ts

@@ -119,6 +119,37 @@ export declare const HANDLER_CONFIG_KEY = "original_js_handler";
  * The name of the compiled middleware file within the .kata directory.
  */
 export declare const MIDDLEWARE_FILE_NAME = "middleware.js";
+/**
+ * Bootstrap handler module name.
+ * The compiled .pyc is at src/python/dist/kata_bootstrap.pyc and is placed
+ * in the config layer at /opt/python/kata_bootstrap.pyc so the Python 3.12
+ * runtime resolves it via PYTHONPATH.
+ *
+ * Using a pre-compiled bootstrap handler prevents SnapStart snapshot failures
+ * caused by import errors in the Lambda Kata Layer (C-bridge, Node.js binary, etc.).
+ * Source: src/python/kata_bootstrap.py — compiled via `yarn build:python`.
+ */
+export declare const BOOTSTRAP_HANDLER_MODULE = "kata_bootstrap";
+/**
+ * Full handler path for the bootstrap handler.
+ * Format: "<module>.<function>" as required by Lambda handler configuration.
+ */
+export declare const BOOTSTRAP_HANDLER_PATH = "kata_bootstrap.handler";
+/**
+ * Resolves the absolute path to the compiled bootstrap handler .pyc file.
+ *
+ * Two resolution paths:
+ * 1. Production (bundled JS / npm package): out/dist/python/kata_bootstrap.pyc
+ *    __dirname = out/dist/ → __dirname/python/kata_bootstrap.pyc
+ * 2. Development (ts-jest / source): src/python/dist/kata_bootstrap.pyc
+ *    __dirname = src/ → __dirname/python/dist/kata_bootstrap.pyc
+ *
+ * @returns Absolute path to kata_bootstrap.pyc
+ * @throws Error if the compiled .pyc is not found (build step was skipped)
+ *
+ * @internal
+ */
+export declare function resolveBootstrapPycPath(): string;
 /**
  * Creates a Lambda Layer containing the kata configuration.
  *

package/out/tsc/src/index.d.ts

@@ -24,8 +24,8 @@ export { resolveAccountId, resolveAccountIdWithSource, isValidAccountIdFormat, A
 export { resolveAccountIdSync, resolveAccountIdSyncWithSource, resolveRegionSync, SyncAccountResolutionError, SyncAccountResolutionResult, SyncAccountResolverOptions, } from './sync-account-resolver';
 export { kata, kataWithAccountId, applyTransformation, handleUnlicensed, isKataTransformed, getKataPromise, extractBundlePathFromHandler, KataWrapperOptions, KataResult, } from './kata-wrapper';
 export { SnapStartActivator, SnapStartActivatorProps, } from './snapstart-construct';
-export { activateSnapStart, SnapStartActivationResult, SnapStartActivatorConfig, } from './snapstart-activator';
-export { createKataConfigLayer, generateConfigContent, KataConfigLayerProps, CONFIG_DIR_NAME, CONFIG_FILE_NAME, HANDLER_CONFIG_KEY, } from './config-layer';
+export { activateSnapStart, handler as snapStartHandler, SnapStartActivationResult, SnapStartActivatorConfig, CustomResourceEvent, CustomResourceResponse, } from './snapstart-activator';
+export { createKataConfigLayer, generateConfigContent, resolveBootstrapPycPath, KataConfigLayerProps, CONFIG_DIR_NAME, CONFIG_FILE_NAME, HANDLER_CONFIG_KEY, BOOTSTRAP_HANDLER_MODULE, BOOTSTRAP_HANDLER_PATH, } from './config-layer';
 export { EnsureNodeRuntimeLayerOptions, EnsureNodeRuntimeLayerResult, NodeVersionInfo, LayerInfo, LayerSearchOptions, LayerRequirements, LayerCreationOptions, Logger, RuntimeDetector, LayerManager, ErrorCodes, NodeRuntimeLayerError, VersionCacheEntry, LayerMetadata, NodejsLayerDeploymentOptions, NodejsLayerDeploymentResult, MultiArchitectureDeploymentResult, } from './nodejs-layer-manager';
 export { DockerRuntimeDetector, DockerRuntimeDetectorOptions, } from './docker-runtime-detector';
 export { AWSLayerManager, AWSLayerManagerOptions, } from './aws-layer-manager';

package/out/tsc/src/snapstart-activator.d.ts

@@ -1,9 +1,7 @@
 /**
  * SnapStart Activator - Custom Resource Handler
  *
- * This module provides the Lambda handler for a CloudFormation Custom Resource
- * that enables SnapStart on Lambda functions after deployment. SnapStart requires
- * asynchronous waiting for snapshot creation, which cannot be done during CDK synthesis.
+ * Enables SnapStart on Lambda functions after deployment via CloudFormation Custom Resource.
  *
  * The activation process:
  * 1. Wait for function to be Active
@@ -11,14 +9,11 @@
  * 3. Wait for configuration update
  * 4. Publish new version (triggers snapshot creation)
  * 5. Wait for snapshot to be ready (up to 3 minutes)
- * 6. Create/update 'kata' alias pointing to the new version
+ * 6. Create/update alias pointing to the new version — ALWAYS, regardless of snapshot outcome
  *
  * @module snapstart-activator
  */
 import { LambdaClient } from '@aws-sdk/client-lambda';
-/**
- * Custom Resource event from CloudFormation.
- */
 export interface CustomResourceEvent {
     RequestType: 'Create' | 'Update' | 'Delete';
     ServiceToken: string;
@@ -38,9 +33,6 @@ export interface CustomResourceEvent {
         AliasName?: string;
     };
 }
-/**
- * Custom Resource response to CloudFormation.
- */
 export interface CustomResourceResponse {
     Status: 'SUCCESS' | 'FAILED';
     Reason?: string;
@@ -55,91 +47,43 @@ export interface CustomResourceResponse {
         OptimizationStatus?: string;
     };
 }
-/**
- * Result of a successful SnapStart activation cycle.
- *
- * Returned by {@link activateSnapStart} after enabling SnapStart,
- * publishing a version, waiting for snapshot readiness, and creating/updating an alias.
- *
- * @see {@link SnapStartActivatorConfig} for configuration options
- */
 export interface SnapStartActivationResult {
-    /** The published Lambda version number (e.g. "42"). */
     version: string;
-    /** The alias name that was created or updated (e.g. "kata"). */
     aliasName: string;
-    /** The full ARN of the alias (e.g. "arn:aws:lambda:us-east-1:123456789012:function:my-fn:kata"). */
     aliasArn: string;
-    /** The SnapStart optimization status of the published version ("On", "Off", or "Unknown"). */
     optimizationStatus: string;
 }
-/**
- * Configuration options for the SnapStart activation cycle.
- *
- * All properties are optional and fall back to sensible defaults.
- *
- * @see {@link activateSnapStart} for the function that consumes this config
- */
 export interface SnapStartActivatorConfig {
-    /**
-     * Maximum time in seconds to wait for snapshot creation before proceeding.
-     * If exceeded, a warning is logged and alias creation continues.
-     * @default 180
-     */
     snapshotTimeoutSeconds?: number;
-    /**
-     * Interval in seconds between polling attempts for snapshot readiness.
-     * @default 2
-     */
     pollingIntervalSeconds?: number;
-    /**
-     * The Lambda alias name to create or update after publishing a version.
-     * @default 'kata'
-     */
     aliasName?: string;
-    /**
-     * @internal Override pre-publish delay in milliseconds (for testing only).
-     * @default 3000
-     */
-    _prePublishDelayMs?: number;
-    /**
-     * @internal Override retry delay in milliseconds (for testing only).
-     * @default 5000
-     */
-    _retryDelayMs?: number;
+    /** @internal */ _prePublishDelayMs?: number;
+    /** @internal */ _retryDelayMs?: number;
 }
-/**
- * Sleep for specified milliseconds.
- * @internal Exported for testability — tests can jest.spyOn to avoid real delays.
- */
+/** @internal Exported for testability — tests can jest.spyOn to avoid real delays. */
 export declare const _testable: {
     sleep(ms: number): Promise<void>;
 };
 /**
  * Activates SnapStart on a Lambda function.
  *
- * This function performs the full SnapStart activation cycle:
- * 1. Ensures function is Active
- * 2. Enables SnapStart configuration
- * 3. Waits for configuration update
- * 4. Publishes new version (with retry on snapshot failure)
- * 5. Waits for snapshot creation
- * 6. Creates/updates alias
- *
- * Steps 3+4 are wrapped in a retry loop: on State: Failed, a new version
- * is published (up to MAX_PUBLISH_RETRIES attempts) to handle transient
- * initialization failures during snapshot creation.
+ * Matches the proven deploy_lambda.py logic:
+ * 1. Ensure function is Active
+ * 2. Enable SnapStart (ApplyOn: PublishedVersions)
+ * 3. Wait for configuration update
+ * 4. Publish ONE version
+ * 5. Poll until snapshot is Active, Failed, or timeout
+ * 6. Create/update alias — ALWAYS, regardless of snapshot outcome
  *
- * @param lambdaClient - AWS Lambda client
- * @param functionName - Name or ARN of the Lambda function
- * @param config - Optional configuration
- * @returns Activation result with version and alias information
+ * No retries. No throws on Failed. Alias is always created.
  */
 export declare function activateSnapStart(lambdaClient: LambdaClient, functionName: string, config?: SnapStartActivatorConfig): Promise<SnapStartActivationResult>;
 /**
- * Lambda handler for CloudFormation Custom Resource.
+ * Custom Resource handler for CloudFormation.
  *
- * This handler is invoked by CloudFormation when the custom resource
- * is created, updated, or deleted.
+ * - Delete → SUCCESS immediately (no action)
+ * - Create/Update → run activateSnapStart → SUCCESS with data
+ * - On error + Update → SUCCESS (prevent rollback deadlock)
+ * - On error + Create → FAILED
  */
 export declare function handler(event: CustomResourceEvent): Promise<CustomResourceResponse>;

package/out/tsc/src/snapstart-construct.d.ts

@@ -43,7 +43,7 @@ export interface SnapStartActivatorProps {
  * 2. Enables SnapStart configuration (`ApplyOn: PublishedVersions`)
  * 3. Publishes a new version (triggers snapshot creation)
  * 4. Polls until the snapshot is ready (or timeout is reached)
- * 5. Creates or updates an alias pointing to the new version
+ * 5. Creates or updates an alias pointing to the new version — ALWAYS, regardless of snapshot outcome
  *
  * After deployment, the published version number and alias ARN are available
  * as CloudFormation attributes via {@link versionRef} and {@link aliasArnRef}.
@@ -107,6 +107,12 @@ export declare class SnapStartActivator extends Construct {
      *
      * This is a self-contained version of the snapstart-activator logic
      * that can be deployed as inline Lambda code.
+     *
+     * Matches the proven deploy_lambda.py reference:
+     * - ONE publish, poll, ALWAYS create alias regardless of snapshot outcome
+     * - No retries on Failed state
+     * - On Update errors → return SUCCESS (prevent rollback deadlock)
+     * - On Create errors → throw (return FAILED)
      */
     private generateHandlerCode;
 }

package/package.json

@@ -1,11 +1,12 @@
 {
   "name": "@lambda-kata/cdk",
-  "version": "0.1.3-rc.80",
+  "version": "0.1.3-rc.84",
   "description": "AWS CDK integration for Lambda Kata - Node.js Lambdas running via Lambda Kata runtime",
   "main": "out/dist/index.js",
   "types": "out/tsc/src/index.d.ts",
   "scripts": {
-    "build": "rm -rf ./dist && rm -rf ./out && rm -rf ./lib && yarn run build:cdk && yarn run types",
+    "build:python": "python3 src/python/compile.py && mkdir -p out/dist/python && cp src/python/dist/kata_bootstrap.pyc out/dist/python/kata_bootstrap.pyc",
+    "build": "rm -rf ./dist && rm -rf ./out && rm -rf ./lib && yarn run build:cdk && yarn run types && yarn run build:python",
     "types": "tsc --emitDeclarationOnly && tsc-alias",
     "build:cdk": "yarn run build:config && node dist/utils/build.js --target=cdk",
     "build:minify": "yarn run build:config && node dist/utils/build.js",