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
The extension now supports trigger compile/preview/apply/destroy/.. operation by two ways:
right clicking on the active editor and select operations in the editor context menu.
open the command palette and type "Kusion: ${OperationName}"
When the active document does not belongs to a stack, a "not in a stack" error message will pop up.
In order to support quickly applying/previewing/... one or more stacks' configuration, when the operation is triggered by the command palette, a quick pick stack list should be provided for users to filter and select.
The probable interaction would be like this:
or if we allow to batch operate multiple stacks in the future:
Enhancement
The extension now supports trigger compile/preview/apply/destroy/.. operation by two ways:
When the active document does not belongs to a stack, a "not in a stack" error message will pop up.
In order to support quickly applying/previewing/... one or more stacks' configuration, when the operation is triggered by the command palette, a quick pick stack list should be provided for users to filter and select.
The probable interaction would be like this:
or if we allow to batch operate multiple stacks in the future:
requirement
kcl-lang/kcl#446
ListProject(workspaceRoot: string): []Project
ListStacks(workspaceRoot: string): []Stack
The text was updated successfully, but these errors were encountered: