You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: packages/aws-cdk/README.md
+2-193Lines changed: 2 additions & 193 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -570,9 +570,8 @@ and might have breaking changes in the future.
570
570
571
571
##### Deploy flowchart
572
572
573
-
The following diagrams illustrate the CDK deployment process at two levels of detail. The first diagram provides a conceptual overview suitable for understanding the high-level flow, while the second diagram shows the technical implementation details for contributors working on the CDK codebase.
574
-
575
-
This flowchart provides a high-level overview of the deployment architecture and key decision points:
573
+
This flowchart provides a high-level overview of the deployment architecture and key decision points.
574
+
For technical implementation details (function calls, file locations), see [docs/deploy-architecture.md](./docs/deploy-architecture.md).
For contributors debugging or modifying the deploy command, this technical flowchart shows the exact function calls and file locations in the execution path.
The deploy process uses a sophisticated work graph (`workGraph.doParallel()` in `work-graph.ts`) to manage parallel execution:
888
-
889
-
-**Asset Building** (concurrency: 1): Compiles Docker images, Lambda code, etc. sequentially to avoid overwhelming system resources
890
-
-**Asset Publishing** (concurrency: 8): Uploads assets to S3/ECR in parallel for faster deployment
891
-
-**Stack Deployment** (configurable): Deploys multiple stacks in parallel while respecting dependencies
892
-
893
-
The dotted lines indicate parallel execution paths from the work graph orchestrator. All operations respect dependency relationships before proceeding (node n45 represents the synchronization point).
894
-
895
704
### `cdk rollback`
896
705
897
706
If a deployment performed using `cdk deploy --no-rollback` fails, your
0 commit comments