KusionStack / KusionStack/vscode-kusion
support project status and operation process view during apply
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 7
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
Feature
support project status view and operation process view during operations(apply/destroy)
Design
the process view will be displayed on the following occasions:
- when the apply/destroy operation is confirmed to trigger until all resources are reconciled.
- user selects the operation item from the operation history.
the project status and operation process view should display information about:
- the metadata of the operation: project name, stack name, the configuration code version(git commit id), the external input(dynamic parameters), target cluster, operator, start time, end time, etc.
- the status of each component in the project: pending/running/failed
- the process of the operation: completed/uncompleted steps, current times taken
- the operation logs
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the existing apply/destroy operation flow and operation-history entry points in the VS Code extension. Review how project and operation data are currently exposed, then define the status and process views around the listed metadata, component states, steps, timings, and logs; done means both confirmed operations and selected history items display the complete information.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- developer-experience, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100