@aws-cdk/toolkit-lib 0.1.0

package/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/NOTICE

@@ -0,0 +1,16 @@
+AWS Cloud Development Kit (AWS CDK)
+Copyright 2018-2025 Amazon.com, Inc. or its affiliates. All Rights Reserved.
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.
+
+Third party attributions of this package can be found in the THIRD_PARTY_LICENSES file

package/README.md

@@ -0,0 +1,432 @@
+# AWS CDK Toolkit Library
+<!--BEGIN STABILITY BANNER-->
+
+---
+
+![@aws-cdk/toolkit-lib: Developer Preview](./assets/toolkit--lib-developer_preview-important.svg)
+
+> The APIs in this module are experimental and under active development.
+> They are subject to non-backward compatible changes or removal in future versions.
+> The package follows the [Semantic Versioning](https://semver.org/) model for [major version zero](https://semver.org/#spec-item-4).
+> Accordingly, breaking changes will be introduced in minor versions and announced in the release notes.
+> This means that while you may use them, you may need to update
+> your source code when upgrading to a newer version of this package.
+
+---
+
+<!--END STABILITY BANNER-->
+
+The AWS Cloud Development Kit (AWS CDK) Toolkit Library enables you to perform CDK actions requiring programmatic access on AWS. You can use the AWS CDK Toolkit Library to implement actions such as bootstrapping, synthesizing, and deploying through code rather than command-line interface (CLI) commands. With this library, you can create custom tools, build specialized CLI applications, and integrate CDK programmatic access capabilities into your development workflows.
+
+## Get started with the AWS CDK Toolkit Library
+
+### Step 1: Install the CDK Toolkit Library
+
+Add the `@aws-cdk/toolkit-lib` package to your code base:
+
+```console
+npm install --save @aws-cdk/toolkit-lib
+```
+
+### Step 2: Create and configure a new instance of the CDK Toolkit
+
+You will use the CDK Toolkit instance to define the actions to perform on your CDK app.
+The following is an example of creating a new instance of the CDK Toolkit:
+
+```ts
+import { Toolkit } from '@aws-cdk/toolkit-lib';
+
+const cdk = new Toolkit({
+   // Optional configuration options go here
+});
+```
+
+You can optionally customize the CDK Toolkit instance during creation.
+For instructions, see [Configure your CDK Toolkit instance](#configure-your-cdk-toolkit-instance).
+
+### Step 3: Create a cloud assembly source for your CDK app
+
+A _Cloud Assembly_ represents the AWS CloudFormation templates and deployment artifacts that are produced from a CDK app.
+With the CDK, the Cloud Assembly is generated during synthesis and is what gets deployed to provision your infrastructure.
+The CDK Toolkit creates a _Cloud Assembly_ from a _Cloud Assembly Source_.
+
+The _Cloud Assembly Source_ is a fundamental CDK Toolkit component that defines instructions for creating a _Cloud Assembly_ from your app.
+For example, CDK apps may need to be synthesized multiple times with additional context values before they are ready.
+Once created, you can use your _Cloud Assembly Source_ to perform actions  with the CDK Toolkit.
+
+The following is an example of creating a _Cloud Assembly Source_ using an inline _assembly builder function_:
+
+```ts
+import * as core from 'aws-cdk-lib/core';
+
+declare const cdk: Toolkit;
+
+const cx = cdk.fromAssemblyBuilder(async () => {
+    const app = new core.App();
+
+    // Define your stacks here
+    new MyStack(app, 'MyStack');
+
+    return app.synth();
+});
+```
+
+For more details, see [Cloud Assembly Sources](#cloud-assembly-sources).
+
+### Step 4: Define programmatic actions in for your CDK app
+
+Now that you’ve created a CDK Toolkit instance and Cloud Assembly Source, you can start to define programmatic actions.
+The following is a basic example that creates a deployment of the `MyStack` stack:
+
+```ts
+declare const cdk: Toolkit;
+declare const cx: ICloudAssemblySource;
+
+await toolkit.deploy(cloudAssembly, {
+    stacks: {
+        strategy: StackSelectionStrategy.PATTERN_MUST_MATCH,
+        patterns: ["MyStack"],
+    },
+});
+```
+
+### Step 5: Customize the CDK Toolkit further
+
+You can configure and customize the CDK Toolkit further for your needs:
+
+* **Messages and requests** - The CDK Toolkit outputs a structured flow of messages and requests back to the client, such as a human actor or application using the CDK Toolkit. For instructions, see [Messages & interaction](#messages--interaction).
+* **Error handling** - The CDK Toolkit uses structured errors to help you identify and handle issues during Toolkit operations. You can integrate error handling into your app or customize them further for your needs. For instructions, see [Error handling](#error-handling).
+
+## Actions
+
+The CDK Toolkit Library provides programmatic interfaces for the following lifecycle actions.
+Support for further actions will be extended over time.
+
+### synth
+
+Synthesis is the process of producing AWS CloudFormation templates and deployment artifacts from a CDK app.
+For an introduction to synthesis, see [Configure and perform CDK stack synthesis](https://docs.aws.amazon.com/cdk/v2/guide/configure-synth.html).
+In the CDK Toolkit Library, you can use synth to produce a reusable snapshot of a _Cloud Assembly Source_.
+This is useful if the same source will be used with multiple Toolkit actions,
+because the _Cloud Assembly_ does not have to be produced multiple times.
+
+```ts
+declare const cdk: Toolkit;
+declare const cx: ICloudAssemblySource;
+
+// Will run the CDK app defined in the Cloud Assembly Source
+// This is an expensive and slow operation
+const cxSnap = await cdk.synth(cx, {
+  validateStacks: true, // set to `false` to not throw an error if stacks in the assembly contain error annotations
+})
+
+// Will use the previously synthesized Cloud Assembly
+// This is now a cheap and fast operation
+const cxSnap = await cdk.list(cxSnap);
+```
+
+You can also use the snapshot to query information about the synthesized _Cloud Assembly_:
+
+```ts
+declare const cloudAssembly = await cxSnap.produce();
+declare const template = cloudAssembly.getStack("my-stack").template;
+```
+
+### list
+
+The list operation provides high-level information about the stacks and their dependencies within a CDK application.
+
+```ts
+declare const cdk: Toolkit;
+declare const cx: ICloudAssemblySource;
+
+const details = await cdk.list(cx, {
+  // optionally provide a stack selector to control which stacks are returned
+  stacks: {
+    strategy: StackSelectionStrategy.PATTERN_MUST_MATCH,
+    patterns: ["my-stack"],
+  }
+});
+```
+
+### deploy
+
+Deployment is the process of provisioning or updating your infrastructure in AWS using the CloudFormation templates and assets produced during synthesis.
+For an introduction to deploying, see [Deploy AWS CDK applications](https://docs.aws.amazon.com/cdk/v2/guide/deploy.html).
+With the CDK Toolkit Library, you can programmatically control deployments, including stack selection, rollback behavior, and deployment monitoring.
+
+```ts
+declare const cdk: Toolkit;
+declare const cx: ICloudAssemblySource;
+
+await cdk.deploy(cx, {
+  deploymentMethod: { method: "direct " }, // use direct deployments instead of change-sets
+  parameters: StackParameters.exactly({ /* ... */ }), // provide new values for stack parameters
+})
+```
+
+### rollback
+
+Rollback returns a stack to its last stable state when a deployment fails or needs to be reversed.
+The CDK Toolkit Library allows you to programmatically roll back failed deployments.
+
+```ts
+declare const cdk: Toolkit;
+declare const cx: ICloudAssemblySource;
+
+await cdk.rollback(cx, {
+  orphanFailedResources: false, // set to `true` to automatically orphan all failed resources
+})
+```
+
+### watch
+
+Use the watch feature to continuously monitor your CDK app for local changes and automatically perform deployments or hotswaps.
+This will create a file watcher that is terminated once your code exits.
+
+```ts
+declare const cdk: Toolkit;
+declare const cx: ICloudAssemblySource;
+
+await cdk.watch(cx, {
+  include: [], // optionally provide a list of file path patterns to watch
+  exclude: [], // or exclude files by file path patterns
+})
+```
+
+### destroy
+
+Use the destroy feature to remove CDK stacks and their associated resources from AWS:
+
+```ts
+declare const cdk: Toolkit;
+declare const cx: ICloudAssemblySource;
+
+await cdk.destroy(cx, {
+  // optionally provide a stack selector to control which stacks are destroyed
+  stacks: {
+    strategy: StackSelectionStrategy.PATTERN_MUST_MATCH,
+    patterns: ["my-stack"],
+  }
+})
+```
+
+## Configure your CDK Toolkit instance
+
+### Messages & interaction
+
+The CDK Toolkit outputs a structured flow of _messages_ and _requests_ back to a client integrating with the Toolkit.
+
+* **Messages** - Informs the client about the progress and state of operations. Does not require a response.
+* **Requests** - Special messages that allow the client to respond. If no response is given, the Toolkit will use a default response.
+
+The CDK Toolkit Library outputs messages and requests through an `IoHost`.
+Think of the `IoHost` as the blueprint that defines how communication works for the CDK Toolkit.
+For each message or request, the Toolkit calls either the `notify` or `requestResponse` method of the `IoHost`.
+
+#### Customizing the IoHost
+
+You can configure a custom `IoHost` to control the flow of information and integrate them into your workflows and automation.
+The following is an example implementation that simply logs all message objects to stdout:
+
+```ts
+const toolkit = new toolkitLib.Toolkit({
+   ioHost: {
+    notify: async function (msg) {
+        console.log(msg);
+    },
+    requestResponse: async function (msg) {
+      console.log(msg);
+      return msg.defaultResponse;
+    }
+  }
+})
+```
+
+The CDK Toolkit awaits the completion of each call, allowing clients to perform asynchronous operations like HTTP requests when handling messages or requests.
+When you implement an `IoHost` interface, you can either process these communications (for example, logging to CloudWatch or prompting users for input) or return immediately without taking action.
+If your implementation doesn’t provide a response to a request, the CDK Toolkit proceeds with a default value.
+
+#### Default IoHost
+
+By default the CDK Toolkit Library will use a `IoHost` implantation that mimics the behavior of the AWS CDK Toolkit CLI.
+
+### Configure your AWS profile
+
+The Toolkit internally uses AWS SDK Clients to make necessary API calls to AWS.
+Authentication configuration is loaded automatically from the environment, but you can explicitly specify the profile to be used:
+
+```ts
+import { Toolkit } from '@aws-cdk/toolkit-lib';
+
+const cdk = new Toolkit({
+  sdkConfig: { profile: "my-profile" },
+});
+```
+
+### Configure a proxy for SDK calls
+
+The Toolkit internally uses AWS SDK Clients to make necessary API calls to AWS.
+You can specify a proxy configuration for all SDK calls:
+
+```ts
+import { Toolkit } from '@aws-cdk/toolkit-lib';
+
+const cdk = new Toolkit({
+  sdkConfig: {
+    httpOptions: {
+      proxyAddress: "https://example.com",
+      caBundlePath: "path/to/ca/bundle",
+    },
+  },
+});
+```
+
+## Configure Toolkit Actions
+
+Every action the CDK Toolkit Library provides has its own options.
+However some arguments and options are shared between multiple actions.
+
+## Cloud Assembly Sources
+
+The _Cloud Assembly Source_ is a fundamental CDK Toolkit component that defines instructions for creating a _Cloud Assembly_ from your app.
+For example, CDK apps may need to be synthesized multiple times with additional context values before they are ready.
+Once created, you can use your _Cloud Assembly Source_ to perform actions  with the CDK Toolkit.
+
+Every _Cloud Assembly Source_ must implement the `ICloudAssemblySource` interface. This allows you to define your own custom sources.
+
+```ts
+interface ICloudAssemblySource {
+  produce(): Promise<cxapi.CloudAssembly>;
+}
+```
+
+For convenience the CDK Toolkit Library offers a range of standard sources, which can be instantiated using the `fromXyz()` helper methods on your toolkit instance.
+
+Most existing CDK apps are written as JavaScript apps or in a jsii language.
+With the CDK Toolkit Library you can use these CDK apps by providing the `app` string as found in a `cdk.json` file:
+
+```ts
+declare const cdk: Toolkit;
+
+// TypeScript
+await cdk.fromCdkApp("ts-node app.ts");
+
+// Python
+await cdk.fromCdkApp("python app.py");
+```
+
+Alternatively a inline `AssemblyBuilder` function can be used to build a CDK app on-the-fly.
+
+```ts
+declare const cdk: Toolkit;
+
+const cx = cdk.fromAssemblyBuilder(async () => {
+    const app = new core.App();
+
+    // Define your stacks here
+    new MyStack(app, 'MyStack');
+
+    return app.synth();
+});
+```
+
+Existing _Cloud Assembly_ directories can be used as source like this:
+
+```ts
+declare const cdk: Toolkit;
+
+const cx = await cdk.fromAssemblyDirectory("cdk.out");
+```
+
+## Stack selection
+
+Most actions of the CDK Toolkit take a `StackSelector` to configure with stacks should be used for the action.
+A `StackSelector` and some optional additional values.
+
+To select all stacks use the `ALL_STACKS` strategy:
+
+```ts
+const allStacks = { strategy: StackSelectionStrategy.ALL_STACKS };
+```
+
+To select only the top-level stacks from the main assembly, use the `MAIN_ASSEMBLY` strategy:
+
+```ts
+const mainStacks = { strategy: StackSelectionStrategy.MAIN_ASSEMBLY };
+```
+
+The `ONLY_SINGLE` strategy allows you to ensure a given assembly contains exactly one stack, and select it:
+
+```ts
+const mainStacks = { strategy: StackSelectionStrategy.ONLY_SINGLE };
+```
+
+To select stacks by IDs, use `PATTERN_MUST_MATCH` with an additional `patterns` property.
+If no stacks are matched, this strategy will throw an error.
+
+```ts
+const matchStacks = {
+  strategy: StackSelectionStrategy.PATTERN_MUST_MATCH,
+  patterns: ["MyStack"],
+};
+```
+
+You can optionally declare that the provided patterns must match exactly one stack by using `PATTERN_MUST_MATCH_SINGLE`,
+or can match none at all by using `PATTERN_MATCH`.
+
+## Error handling
+
+The CDK Toolkit uses structured errors to help you identify and handle issues during CDK Toolkit operations.
+These errors provide detailed information about what went wrong and why.
+
+Each error includes one of the following sources, which represents where the error originates from:
+
+* toolkit - Error originates from the CDK Toolkit.
+* user - Error originates from the user, such as configuration or user input errors.
+
+Each error also includes a specific error type, such as authentication or validation, and a descriptive message. You can catch and handle these errors in your application to provide appropriate responses or fallback behaviors. If the CDK Toolkit throws other exceptions, they are bugs and you should report them by raising an issue.s
+
+### How to handle errors
+
+In the CDK Toolkit Library, all errors are thrown as regular exceptions.
+
+Use helper methods provided by the CDK Toolkit to detect error types.
+Even though errors are typed, do not rely on instanceof checks because they can behave unexpectedly when working with multiple copies of the same package.
+
+The following is a basic example:
+
+```ts
+declare const cdk: Toolkit;
+declare const cx: ICloudAssemblySource;
+
+try {
+  // Attempt a CDK Toolkit operation
+  const deployment = await cdk.deploy(cloudAssembly, {
+      stacks: ['MyStack']
+  });
+
+} catch (error) {
+
+  if (ToolkitError.isAuthenticationError(error)) {
+    // Handle credential issues
+    console.error('AWS credentials error:', error.message);
+
+  } else if (ToolkitError.isAssemblyError(error)) {
+    // Handle errors from your CDK app
+    console.error('CDK app error:', error.message);
+
+  } else if (ToolkitError.isContextProviderError(error)) {
+    // Handle errors from context providers
+    console.error('Context provider error:', error.message);
+
+  } else if (ToolkitError.isToolkitError(error)) {
+    // Handle all other Toolkit errors
+    console.error('Generic Toolkit error:', error.message);
+
+  } else {
+      // Handle unexpected errors
+      console.error('Unexpected error:', error);
+  }
+}
+```

package/build-info.json

@@ -0,0 +1,4 @@
+{
+  "comment": "Generated at 2025-02-24T19:44:09Z by generate.sh",
+  "commit": "50b14fd"
+}