@codedrifters/configulator 0.0.456 → 0.0.458

package/lib/index.d.mts

@@ -8838,6 +8838,11 @@ interface CdkDiffOptions extends CdkGlobalOptions {
 }
 /**
  * Options for the `cdk bootstrap` command.
+ *
+ * Bootstrap's trailing positional arguments are **environment specifiers**
+ * (`aws://<account>/<region>`), not stack patterns. They are carried by the
+ * inherited {@link CdkGlobalOptions.stackPatterns} field, which is the shared
+ * vehicle for every command's trailing positionals.
  */
 interface CdkBootstrapOptions extends CdkGlobalOptions {
     /*****************************************************************************
@@ -9900,6 +9905,23 @@ declare class AwsDeploymentTarget extends Component {
      *
      ****************************************************************************/
     private configureDestroyTask;
+    /*****************************************************************************
+     *
+     * Bootstrap Tasks
+     *
+     * Unlike deploy / watch / destroy, this family is generated for **every**
+     * target rather than only those with `localDeployment` enabled. Bootstrapping
+     * provisions the CDK toolkit stack for one account/region pair, and a
+     * CI-only target needs that done before its first deployment just as much as
+     * a local one — gating on `localDeployment` would also make the built-in
+     * `prod` default (`--termination-protection`) unreachable, since prod targets
+     * default to `localDeployment: false`.
+     *
+     * The tasks are never invoked automatically; running one is always a
+     * deliberate, elevated-credentials operation.
+     *
+     ****************************************************************************/
+    private configureBootstrapTask;
 }
 
 /*******************************************************************************
@@ -10204,6 +10226,31 @@ declare class AwsDeploymentConfig extends Component {
      * - Change the output location for easier workflows.
      *
      ****************************************************************************/
+    /**
+     * Resolve the synth options for the project-wide `synth` / `synth:silent`
+     * tasks.
+     *
+     * `cdk synth` produces one cloud assembly that every target deploys from, so
+     * there is no single target to resolve against. Each registered target's
+     * resolved options are folded together lowest-stage-first, so a higher stage
+     * wins scalar collisions and arrays/records union across targets. Sorting
+     * makes the result independent of the order targets were declared in. With a
+     * single target this is exactly `synthOptionsFor(target)`; with none it is
+     * empty.
+     */
+    private resolveSynthOptions;
+    /**
+     * (Re)build the project-wide synth tasks.
+     *
+     * Idempotent — it resets both tasks before rebuilding them, so it is safe to
+     * run once from the constructor (keeping the tasks well-formed for a project
+     * with no targets) and again from `preSynthesize`, once every target has
+     * registered itself and the override chain can actually be resolved.
+     *
+     * `--output` is pinned at the call site because it is a property of the
+     * project layout, and `--quiet` is pinned on `synth:silent` because it is
+     * what makes that task silent. Every other flag flows through the chain.
+     */
     private configureSynthTask;
     preSynthesize(): void;
 }
@@ -10299,8 +10346,12 @@ declare const CDK_DEPLOY_DEFAULTS_BY_STAGE: Record<AwsStageType, Partial<CdkDepl
 /**
  * Per-stage defaults for `cdk synth`.
  *
- * Every stage runs synth with `--quiet` so the synthesised template stays out
- * of normal task logs.
+ * Deliberately empty. `--quiet` is what distinguishes the generated `synth`
+ * task from `synth:silent`, so it is pinned at the `synth:silent` call site
+ * rather than seeded here — a per-stage default would silence both tasks and
+ * collapse them into the same command. Consumers that genuinely want a quiet
+ * `synth` can still set `synthDefaults[stage].quiet`, which reaches the
+ * rendered command; `synth:silent` stays silent regardless.
  */
 declare const CDK_SYNTH_DEFAULTS_BY_STAGE: Record<AwsStageType, Partial<CdkSynthOptions>>;
 /**
@@ -12475,7 +12526,7 @@ interface PnpmWorkspaceOptions {
      * specifiers — git, tarball URL, local path — are rejected. Direct
      * dependencies are unaffected.
      *
-     * @default undefined (key omitted; pnpm 11 defaults to true)
+     * @default undefined (key omitted; pnpm 11 defaults to false)
      *
      * @see https://pnpm.io/settings#blockexoticsubdeps
      */

package/lib/index.d.ts

@@ -8887,6 +8887,11 @@ interface CdkDiffOptions extends CdkGlobalOptions {
 }
 /**
  * Options for the `cdk bootstrap` command.
+ *
+ * Bootstrap's trailing positional arguments are **environment specifiers**
+ * (`aws://<account>/<region>`), not stack patterns. They are carried by the
+ * inherited {@link CdkGlobalOptions.stackPatterns} field, which is the shared
+ * vehicle for every command's trailing positionals.
  */
 interface CdkBootstrapOptions extends CdkGlobalOptions {
     /*****************************************************************************
@@ -9949,6 +9954,23 @@ declare class AwsDeploymentTarget extends Component {
      *
      ****************************************************************************/
     private configureDestroyTask;
+    /*****************************************************************************
+     *
+     * Bootstrap Tasks
+     *
+     * Unlike deploy / watch / destroy, this family is generated for **every**
+     * target rather than only those with `localDeployment` enabled. Bootstrapping
+     * provisions the CDK toolkit stack for one account/region pair, and a
+     * CI-only target needs that done before its first deployment just as much as
+     * a local one — gating on `localDeployment` would also make the built-in
+     * `prod` default (`--termination-protection`) unreachable, since prod targets
+     * default to `localDeployment: false`.
+     *
+     * The tasks are never invoked automatically; running one is always a
+     * deliberate, elevated-credentials operation.
+     *
+     ****************************************************************************/
+    private configureBootstrapTask;
 }
 
 /*******************************************************************************
@@ -10253,6 +10275,31 @@ declare class AwsDeploymentConfig extends Component {
      * - Change the output location for easier workflows.
      *
      ****************************************************************************/
+    /**
+     * Resolve the synth options for the project-wide `synth` / `synth:silent`
+     * tasks.
+     *
+     * `cdk synth` produces one cloud assembly that every target deploys from, so
+     * there is no single target to resolve against. Each registered target's
+     * resolved options are folded together lowest-stage-first, so a higher stage
+     * wins scalar collisions and arrays/records union across targets. Sorting
+     * makes the result independent of the order targets were declared in. With a
+     * single target this is exactly `synthOptionsFor(target)`; with none it is
+     * empty.
+     */
+    private resolveSynthOptions;
+    /**
+     * (Re)build the project-wide synth tasks.
+     *
+     * Idempotent — it resets both tasks before rebuilding them, so it is safe to
+     * run once from the constructor (keeping the tasks well-formed for a project
+     * with no targets) and again from `preSynthesize`, once every target has
+     * registered itself and the override chain can actually be resolved.
+     *
+     * `--output` is pinned at the call site because it is a property of the
+     * project layout, and `--quiet` is pinned on `synth:silent` because it is
+     * what makes that task silent. Every other flag flows through the chain.
+     */
     private configureSynthTask;
     preSynthesize(): void;
 }
@@ -10348,8 +10395,12 @@ declare const CDK_DEPLOY_DEFAULTS_BY_STAGE: Record<AwsStageType, Partial<CdkDepl
 /**
  * Per-stage defaults for `cdk synth`.
  *
- * Every stage runs synth with `--quiet` so the synthesised template stays out
- * of normal task logs.
+ * Deliberately empty. `--quiet` is what distinguishes the generated `synth`
+ * task from `synth:silent`, so it is pinned at the `synth:silent` call site
+ * rather than seeded here — a per-stage default would silence both tasks and
+ * collapse them into the same command. Consumers that genuinely want a quiet
+ * `synth` can still set `synthDefaults[stage].quiet`, which reaches the
+ * rendered command; `synth:silent` stays silent regardless.
  */
 declare const CDK_SYNTH_DEFAULTS_BY_STAGE: Record<AwsStageType, Partial<CdkSynthOptions>>;
 /**
@@ -12524,7 +12575,7 @@ interface PnpmWorkspaceOptions {
      * specifiers — git, tarball URL, local path — are rejected. Direct
      * dependencies are unaffected.
      *
-     * @default undefined (key omitted; pnpm 11 defaults to true)
+     * @default undefined (key omitted; pnpm 11 defaults to false)
      *
      * @see https://pnpm.io/settings#blockexoticsubdeps
      */

package/lib/index.js

@@ -38071,9 +38071,9 @@ var CDK_DEPLOY_DEFAULTS_BY_STAGE = {
   }
 };
 var CDK_SYNTH_DEFAULTS_BY_STAGE = {
-  dev: { quiet: true },
-  stage: { quiet: true },
-  prod: { quiet: true }
+  dev: {},
+  stage: {},
+  prod: {}
 };
 var CDK_WATCH_DEFAULTS_BY_STAGE = {
   dev: { progress: "events" },
@@ -38799,6 +38799,11 @@ var TURBO_RUN_DRY_RUN = {
 };
 
 // src/aws/aws-deployment-config.ts
+var SYNTH_STAGE_RANK = {
+  [import_utils9.AWS_STAGE_TYPE.DEV]: 0,
+  [import_utils9.AWS_STAGE_TYPE.STAGE]: 1,
+  [import_utils9.AWS_STAGE_TYPE.PROD]: 2
+};
 var AwsDeploymentConfig = class _AwsDeploymentConfig extends import_projen12.Component {
   constructor(project) {
     super(project);
@@ -38814,15 +38819,55 @@ var AwsDeploymentConfig = class _AwsDeploymentConfig extends import_projen12.Com
      * - Change the output location for easier workflows.
      *
      ****************************************************************************/
+    /**
+     * Resolve the synth options for the project-wide `synth` / `synth:silent`
+     * tasks.
+     *
+     * `cdk synth` produces one cloud assembly that every target deploys from, so
+     * there is no single target to resolve against. Each registered target's
+     * resolved options are folded together lowest-stage-first, so a higher stage
+     * wins scalar collisions and arrays/records union across targets. Sorting
+     * makes the result independent of the order targets were declared in. With a
+     * single target this is exactly `synthOptionsFor(target)`; with none it is
+     * empty.
+     */
+    this.resolveSynthOptions = () => {
+      const ordered = [...this.awsDeploymentTargets].sort(
+        (a, b) => SYNTH_STAGE_RANK[a.awsStageType] - SYNTH_STAGE_RANK[b.awsStageType] || a.account.localeCompare(b.account) || a.region.localeCompare(b.region)
+      );
+      return mergeCdkOptions(
+        ...ordered.map((target) => this.cdkCli.synthOptionsFor(target))
+      );
+    };
+    /**
+     * (Re)build the project-wide synth tasks.
+     *
+     * Idempotent — it resets both tasks before rebuilding them, so it is safe to
+     * run once from the constructor (keeping the tasks well-formed for a project
+     * with no targets) and again from `preSynthesize`, once every target has
+     * registered itself and the override chain can actually be resolved.
+     *
+     * `--output` is pinned at the call site because it is a property of the
+     * project layout, and `--quiet` is pinned on `synth:silent` because it is
+     * what makes that task silent. Every other flag flows through the chain.
+     */
     this.configureSynthTask = () => {
+      const synthOpts = this.resolveSynthOptions();
       this.project.tasks.tryFind("synth")?.reset(`rm -rf ${this.cdkOut}`);
-      this.project.tasks.tryFind("synth")?.exec(`cdk ${renderCdkSynth({ output: this.cdkOut })}`, {
+      this.project.tasks.tryFind("synth")?.exec(`cdk ${renderCdkSynth({ ...synthOpts, output: this.cdkOut })}`, {
         env: this.env
       });
       this.project.tasks.tryFind("synth:silent")?.reset(`rm -rf ${this.cdkOut}`);
-      this.project.tasks.tryFind("synth:silent")?.exec(`cdk ${renderCdkSynth({ output: this.cdkOut, quiet: true })}`, {
-        env: this.env
-      });
+      this.project.tasks.tryFind("synth:silent")?.exec(
+        `cdk ${renderCdkSynth({
+          ...synthOpts,
+          output: this.cdkOut,
+          quiet: true
+        })}`,
+        {
+          env: this.env
+        }
+      );
     };
     this.cdkCli = CdkCli.of(project) || new CdkCli(project);
     this.env = {
@@ -38912,6 +38957,7 @@ var AwsDeploymentConfig = class _AwsDeploymentConfig extends import_projen12.Com
   }
   preSynthesize() {
     super.preSynthesize();
+    this.configureSynthTask();
     if (TurboRepo.of(this.project)) {
       const turbo = TurboRepo.of(this.project);
       turbo.postCompileTask?.outputs.push((0, import_node_path2.join)(this.cdkOut, "**"));
@@ -39042,6 +39088,41 @@ var AwsDeploymentTarget = class _AwsDeploymentTarget extends import_projen13.Com
         );
       }
     };
+    /*****************************************************************************
+     *
+     * Bootstrap Tasks
+     *
+     * Unlike deploy / watch / destroy, this family is generated for **every**
+     * target rather than only those with `localDeployment` enabled. Bootstrapping
+     * provisions the CDK toolkit stack for one account/region pair, and a
+     * CI-only target needs that done before its first deployment just as much as
+     * a local one — gating on `localDeployment` would also make the built-in
+     * `prod` default (`--termination-protection`) unreachable, since prod targets
+     * default to `localDeployment: false`.
+     *
+     * The tasks are never invoked automatically; running one is always a
+     * deliberate, elevated-credentials operation.
+     *
+     ****************************************************************************/
+    this.configureBootstrapTask = () => {
+      const taskName = [
+        "bootstrap",
+        this.awsStageType,
+        this.account,
+        this.region
+      ].join(":");
+      const bootstrapTask = this.project.tasks.addTask(taskName, {
+        env: this.awsDeploymentConfig.env
+      });
+      const bootstrapOpts = this.awsDeploymentConfig.cdkCli.bootstrapOptionsFor(this);
+      bootstrapTask.exec(
+        `cdk ${renderCdkBootstrap({
+          ...bootstrapOpts,
+          profile: this.localDeploymentConfig?.profile,
+          stackPatterns: [`aws://${this.account}/${this.region}`]
+        })}`
+      );
+    };
     this.account = options.account;
     this.region = options.region;
     this.cdkOptions = options.cdkOptions;
@@ -39085,6 +39166,7 @@ var AwsDeploymentTarget = class _AwsDeploymentTarget extends import_projen13.Com
     this.configureDeployTask();
     this.configureWatchTask();
     this.configureDestroyTask();
+    this.configureBootstrapTask();
   }
   /**
    * Static method to discovert targets in a project.