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
Currently, the AWS Toolkit for VS Code provides Step Functions Workflow Studio through the App Composer integration, which generates SAM-compatible state machine definitions. While this is great for SAM users, CDK users cannot directly benefit from this visual workflow editor.
Problem
When working with Step Functions in CDK:
You have to write ASL JSON definitions manually or maintain them in separate files
There's no visual editor integration for CDK-based state machines
The current Workflow Studio integration only works for SAM applications, generating complete SAM applications rather than just the workflow definition
Proposed Solution
Add support for CDK workflows in the VS Code Workflow Studio by:
Allowing users to edit just the workflow definition part without generating a complete SAM application
Providing an option to export the ASL definition in a format that can be directly used with CDK's StateMachine construct
Supporting round-trip editing where CDK users can:
Open existing ASL definitions in Workflow Studio
Make visual changes
Save back to their CDK project
Additional Context
The community has recognized this need, leading to third-party solutions like @mbonig/state-machine. However, having this capability built into the AWS Toolkit would provide a more integrated and maintainable solution.
The text was updated successfully, but these errors were encountered:
Current Situation
Currently, the AWS Toolkit for VS Code provides Step Functions Workflow Studio through the App Composer integration, which generates SAM-compatible state machine definitions. While this is great for SAM users, CDK users cannot directly benefit from this visual workflow editor.
Problem
When working with Step Functions in CDK:
Proposed Solution
Add support for CDK workflows in the VS Code Workflow Studio by:
StateMachine
constructAdditional Context
The community has recognized this need, leading to third-party solutions like @mbonig/state-machine. However, having this capability built into the AWS Toolkit would provide a more integrated and maintainable solution.
The text was updated successfully, but these errors were encountered: