@codedrifters/configulator 0.0.441 → 0.0.442

package/lib/index.d.mts

@@ -12910,6 +12910,15 @@ declare class AwsDeployWorkflow extends Component {
      * blocker rather than a cosmetic one: the apply requires a successful plan
      * run, so one from-scratch target blocks applying any plan for the stage.
      *
+     * A genuinely absent stack fails the same way for a different reason:
+     * `CreateChangeSet` resolves `AWS::SSM::Parameter::Value` template
+     * parameters when the change set is created, so a never-deployed stack that
+     * consumes parameters written by other not-yet-deployed stacks cannot get a
+     * `CREATE` change set at all (`Unable to fetch parameters [...] from
+     * parameter store for this account`). That deadlocks the first deployment of
+     * an entire stage: no green plan without the upstream stacks, no upstream
+     * stacks without an apply, no apply without a green plan.
+     *
      * `cdk list --long --json` resolves the pattern to CloudFormation stack names
      * out of the built assembly's manifest — no synth, no cloud call — and each
      * name costs one `describe-stacks`, which needs only
@@ -12917,17 +12926,16 @@ declare class AwsDeployWorkflow extends Component {
      * already carries it. A `cdk list` that fails contributes no names, leaving
      * the diff to run exactly as it does today.
      *
-     * A genuinely absent stack keeps the configured method — CDK gives it a
-     * `CREATE` change set and diffs it fine. Only a tombstone moves the method,
-     * and only to `template`, never to `auto`: `auto` would swallow a real
-     * permission failure and present a degraded diff as authoritative, which is
-     * what an explicit `change-set` pin exists to prevent. `template`
-     * over-reporting replacements is vacuous here, because every resource in a
-     * stack built from scratch is an add.
+     * Both from-scratch arms therefore move the method, and only to `template`,
+     * never to `auto`: `auto` would swallow a real permission failure and
+     * present a degraded diff as authoritative, which is what an explicit
+     * `change-set` pin exists to prevent. `template` over-reporting replacements
+     * is vacuous here, because every resource in a stack built from scratch is
+     * an add. A stack in any other status keeps the configured method.
      *
      * The method is per invocation, not per stack — `cdk diff` diffs everything
      * its pattern matches in one pass. A pattern matching several stacks where
-     * only one is a tombstone therefore diffs all of them with `template`, and
+     * only one is from-scratch therefore diffs all of them with `template`, and
      * the banner names the stack that caused it.
      */
     private diffProbeLines;

package/lib/index.d.ts

@@ -12959,6 +12959,15 @@ declare class AwsDeployWorkflow extends Component {
      * blocker rather than a cosmetic one: the apply requires a successful plan
      * run, so one from-scratch target blocks applying any plan for the stage.
      *
+     * A genuinely absent stack fails the same way for a different reason:
+     * `CreateChangeSet` resolves `AWS::SSM::Parameter::Value` template
+     * parameters when the change set is created, so a never-deployed stack that
+     * consumes parameters written by other not-yet-deployed stacks cannot get a
+     * `CREATE` change set at all (`Unable to fetch parameters [...] from
+     * parameter store for this account`). That deadlocks the first deployment of
+     * an entire stage: no green plan without the upstream stacks, no upstream
+     * stacks without an apply, no apply without a green plan.
+     *
      * `cdk list --long --json` resolves the pattern to CloudFormation stack names
      * out of the built assembly's manifest — no synth, no cloud call — and each
      * name costs one `describe-stacks`, which needs only
@@ -12966,17 +12975,16 @@ declare class AwsDeployWorkflow extends Component {
      * already carries it. A `cdk list` that fails contributes no names, leaving
      * the diff to run exactly as it does today.
      *
-     * A genuinely absent stack keeps the configured method — CDK gives it a
-     * `CREATE` change set and diffs it fine. Only a tombstone moves the method,
-     * and only to `template`, never to `auto`: `auto` would swallow a real
-     * permission failure and present a degraded diff as authoritative, which is
-     * what an explicit `change-set` pin exists to prevent. `template`
-     * over-reporting replacements is vacuous here, because every resource in a
-     * stack built from scratch is an add.
+     * Both from-scratch arms therefore move the method, and only to `template`,
+     * never to `auto`: `auto` would swallow a real permission failure and
+     * present a degraded diff as authoritative, which is what an explicit
+     * `change-set` pin exists to prevent. `template` over-reporting replacements
+     * is vacuous here, because every resource in a stack built from scratch is
+     * an add. A stack in any other status keeps the configured method.
      *
      * The method is per invocation, not per stack — `cdk diff` diffs everything
      * its pattern matches in one pass. A pattern matching several stacks where
-     * only one is a tombstone therefore diffs all of them with `template`, and
+     * only one is from-scratch therefore diffs all of them with `template`, and
      * the banner names the stack that caused it.
      */
     private diffProbeLines;

package/lib/index.js

@@ -43398,6 +43398,15 @@ var AwsDeployWorkflow = class _AwsDeployWorkflow extends import_projen29.Compone
      * blocker rather than a cosmetic one: the apply requires a successful plan
      * run, so one from-scratch target blocks applying any plan for the stage.
      *
+     * A genuinely absent stack fails the same way for a different reason:
+     * `CreateChangeSet` resolves `AWS::SSM::Parameter::Value` template
+     * parameters when the change set is created, so a never-deployed stack that
+     * consumes parameters written by other not-yet-deployed stacks cannot get a
+     * `CREATE` change set at all (`Unable to fetch parameters [...] from
+     * parameter store for this account`). That deadlocks the first deployment of
+     * an entire stage: no green plan without the upstream stacks, no upstream
+     * stacks without an apply, no apply without a green plan.
+     *
      * `cdk list --long --json` resolves the pattern to CloudFormation stack names
      * out of the built assembly's manifest — no synth, no cloud call — and each
      * name costs one `describe-stacks`, which needs only
@@ -43405,17 +43414,16 @@ var AwsDeployWorkflow = class _AwsDeployWorkflow extends import_projen29.Compone
      * already carries it. A `cdk list` that fails contributes no names, leaving
      * the diff to run exactly as it does today.
      *
-     * A genuinely absent stack keeps the configured method — CDK gives it a
-     * `CREATE` change set and diffs it fine. Only a tombstone moves the method,
-     * and only to `template`, never to `auto`: `auto` would swallow a real
-     * permission failure and present a degraded diff as authoritative, which is
-     * what an explicit `change-set` pin exists to prevent. `template`
-     * over-reporting replacements is vacuous here, because every resource in a
-     * stack built from scratch is an add.
+     * Both from-scratch arms therefore move the method, and only to `template`,
+     * never to `auto`: `auto` would swallow a real permission failure and
+     * present a degraded diff as authoritative, which is what an explicit
+     * `change-set` pin exists to prevent. `template` over-reporting replacements
+     * is vacuous here, because every resource in a stack built from scratch is
+     * an add. A stack in any other status keeps the configured method.
      *
      * The method is per invocation, not per stack — `cdk diff` diffs everything
      * its pattern matches in one pass. A pattern matching several stacks where
-     * only one is a tombstone therefore diffs all of them with `template`, and
+     * only one is from-scratch therefore diffs all of them with `template`, and
      * the banner names the stack that caused it.
      */
     this.diffProbeLines = (target, outputFile) => {
@@ -43437,7 +43445,8 @@ var AwsDeployWorkflow = class _AwsDeployWorkflow extends import_projen29.Compone
         '  status=$(aws cloudformation describe-stacks --stack-name "$stack" --query "Stacks[0].StackStatus" --output text 2>/dev/null || echo NOT_FOUND)',
         '  case "$status" in',
         "    NOT_FOUND|REVIEW_IN_PROGRESS)",
-        `      echo "${DIFF_NEW_STACK_MARKER} \u2014 $stack does not exist yet, so this target will be created from scratch." | tee -a ${outputFile}`,
+        `      method=${CDK_DIFF_METHOD.Template}`,
+        `      echo "${DIFF_NEW_STACK_MARKER} \u2014 $stack does not exist yet, so this target will be created from scratch. Diffing it with --method=${CDK_DIFF_METHOD.Template}." | tee -a ${outputFile}`,
         "      ;;",
         "    ROLLBACK_COMPLETE|ROLLBACK_FAILED)",
         `      method=${CDK_DIFF_METHOD.Template}`,