@emarketeer/ts-microservice-commons 10.4.0 → 10.5.1

package/dist/cdk/cjs/index.js

@@ -412,6 +412,7 @@ const RECAP_DEV_TIMEOUT_WINDOW_SECONDS = 300;
  */
 const buildBaseEnvironment = (stage, scope) => ({
     STAGE: stage,
+    stage,
     NODE_ENV: stage === 'prod' ? 'production' : 'development',
     REGION: cdk.Stack.of(scope).region,
 });
@@ -536,11 +537,13 @@ function getHandlerBundlerPath() {
  * - Otherwise bundles `entryFile` via the project handler bundler at synth
  *   time, with overrides applied on top of the defaults.
  *
- * An explicit `assetHash` is derived from the entry path + bundling overrides.
- * Without it, multiple handlers under the same source directory (the common
- * `src/handlers/` layout) would share an asset — CDK would run `tryBundle`
- * once and reuse that asset for every other lambda, silently dropping
- * per-function overrides. The explicit hash gives each handler a unique asset.
+ * An explicit `assetHash` is derived per call from the entry path, bundling
+ * overrides, and a synth-time timestamp. The entry path is required so that
+ * multiple handlers under the same source directory (the common
+ * `src/handlers/` layout) don't collapse into one asset — without it, CDK
+ * would run `tryBundle` once and silently reuse the same code for every
+ * lambda. The timestamp forces a fresh asset on every synth so each deploy
+ * uploads a clean rebuild rather than reusing a cached upload.
  */
 function resolveLambdaCode(options) {
     if (options.codePath) {
@@ -559,6 +562,7 @@ function resolveLambdaCode(options) {
     const hash = crypto.createHash('sha256')
         .update(entry)
         .update(JSON.stringify(overrides ?? {}))
+        .update(String(Date.now()))
         .digest('hex');
     const assetHash = `${handlerName}-${hash}`;
     return awsLambda.Code.fromAsset(path__namespace.dirname(entry), {