aws-cdk 2.1028.0 → 2.1029.0

package/README.md

@@ -1131,13 +1131,17 @@ apply the refactor on your CloudFormation stacks. But for now, only the dry-run
 mode is supported.
 
 If your application has more than one stack, and you want the `refactor`
-command to consider only a subset of them, you can pass a list of stack
-patterns as a parameter:
+command to consider only a subset of them, you can specify the stacks you
+want, both local and deployed:
 
 ```shell
-$ cdk refactor Web* --unstable=refactor --dry-run 
+$ cdk refactor --local-stack Foo --local-stack Bar --deployed-stack Foo --unstable=refactor --dry-run 
 ```
 
+This is useful if, for example, you have more than one CDK application deployed
+to a given environment, and you want to only include the deployed stacks that
+belong to the application that you are refactoring.
+
 The pattern language is the same as the one used in the `cdk deploy` command.
 However, unlike `cdk deploy`, in the absence of this parameter, all stacks are
 considered.
@@ -1191,6 +1195,12 @@ resource currently deployed, while the destination must refer to a location
 that is not already occupied by any resource.
 
 
+#### Limitations
+- A refactor cannot leave a stack empty. This is a CloudFormation API limitation, 
+  that also applies to deployments.
+- Creation of new stacks during a refactor is not supported. If you need to
+  create a new stack, do it in a separate deployment, previous to refactoring.
+
 ### `cdk drift`
 
 Checks if there is any drift in your stack or stacks. If you need the command

package/build-info.json

@@ -1,4 +1,4 @@
 {
-  "comment": "Generated at 2025-09-03T16:02:21Z by generate.sh",
-  "commit": "e7ea9d5"
+  "comment": "Generated at 2025-09-05T14:18:23Z by generate.sh",
+  "commit": "aef751e"
 }

package/lib/cli/cdk-toolkit.d.ts

@@ -644,11 +644,15 @@ export interface RefactorOptions {
      */
     overrideFile?: string;
     /**
-     * Modifies the behavior of the `mappingFile` option by swapping source and
+     * Modifies the behavior of the `overrideFile` option by swapping source and
      * destination locations. This is useful when you want to undo a refactor
      * that was previously applied.
      */
     revert?: boolean;
+    /**
+     * Whether to do the refactor without prompting the user for confirmation.
+     */
+    force?: boolean;
     /**
      * Criteria for selecting stacks to compare with the deployed stacks in the
      * target environment.
@@ -658,6 +662,10 @@ export interface RefactorOptions {
      * A list of names of additional deployed stacks to be included in the comparison.
      */
     additionalStackNames?: string[];
+    /**
+     * Role to assume in the target environment before performing the refactor.
+     */
+    roleArn?: string;
 }
 /**
  * Options for the drift command