-
- -
-
# DevStream
-[](https://makeapullrequest.com)
-
-[](https://goreportcard.com/report/github.com/devstream-io/devstream)
-[](https://github.com/devstream-io/devstream/releases)
-[](https://bestpractices.coreinfrastructure.org/projects/6202)
-[](https://cloud-native.slack.com/archives/C03LA2B8K0A)
-
-| English | [中文](README_zh.md) |
-| --- | --- |
-
-
-
-## DevStream, What Is It Anyway?
-
-TL;DR: DevStream (CLI tool named `dtm`) is an open-source DevOps toolchain manager.
-
-[v0.6.0 Demo](https://www.youtube.com/watch?v=q7TK3vFr1kg)
-
-Imagine you are starting a new project or ramping up a new team. Before writing the first line of code, you have to figure out the tools to run an effective SDLC process and from development to deployment.
-
-Typically, you'd need the following pieces in place to work effectively:
-
-- Project management software or issue tracking tools (JIRA, etc.)
-- Source code management (GitHub, Bitbucket, etc.)
-- Continuous integration tools (Jenkins, CircleCI, Travis CI, etc.)
-- Continuous delivery/deployment tools (Flux CD/Flux2, Argo CD, etc.)
-- A single source of truth for secrets and credentials (secrets manager, e.g., Vault by HashiCorp)
-- Some tools for centralized logging and monitoring (for example, ELK, Prometheus/Grafana);
-
-The list could go on for quite a bit, but you get the idea!
-
-There are many challenges in creating an effective and personalized workflow:
-
-- There are too many choices. Which is best? There is no "one-size-fits-all" answer because it totally depends on your needs and preferences.
-- Integration between different pieces is challenging, creating silos and fragmentation.
-- The software world evolves fast. What's best today might not make sense tomorrow. If you want to switch parts or tools out, it can be challenging and resource intensive to manage.
-
-To be fair, there are a few integrated products out there that may contain everything you might need, but they might not suit your specific requirements perfectly. So, the chances are, you will still want to go out and do your research, find the best pieces, and integrate them yourself. That being said, to choose, launch, connect, and manage all these pieces take a lot of time and energy.
-
-You might be seeing where we are going with this...
-
-We wanted to make it easy to set up these personalized and flexible toolchains, so we built DevStream, an open-source DevOps toolchain manager.
-
-Think of the Linux kernel V.S. different distributions. Different distros offer different packages so that you can always choose the best for your need.
-
-Or, think of `yum`, `apt`, or `apk`. You can easily set it up with your favorite packages for any new environment using these package managers.
-
-DevStream aims to be the package manager for DevOps tools.
-
-To be more ambitious, DevStream wants to be the Linux kernel, around which different distros can be created with various components so that you can always have the best components for each part of your SDLC workflow.
-
-## Why `dtm`?
-
-Q: The CLI tool is named `dtm`, while the tool itself is called DevStream. What the heck?! Where is the consistency?
-
-A: Inspired by [`git`](https://github.com/git/git#readme), the name is (depending on your mood):
-
-- a symmetric, scientific acronym of **d**evs**t**rea**m**.
-- "devops toolchain manager": you're in a good mood, and it actually works for you.
-- "dead to me": when it breaks.
-
-## Why Use DevStream?
-
-No more manual curl/wget download, apt install, helm install; no more local experiments and playing around just to get a piece of tool installed correctly.
-
-Define your desired DevOps tools in a single human-readable YAML config file, and at the press of a button (one single command), you will have your whole DevOps toolchain and SDLC workflow set up. Five Minutes. One Command.
-
-Want to install another different tool for a try? No problem.
-
-Want to remove or reinstall a specific piece in the workflow? DevStream has got your back!
-
-## Quick Start
-
-If you want to get a quick start, follow our [quick start](https://docs.devstream.io/en/latest/quickstart/) doc now.
-
-## Best Practices Toolchain Integration
-
-DevStream supports the management of many tools. You can flexibly combine some tools to meet the DevOps toolchain your need.
-
-And yes, if you ask me if any recommended practices that can be used out of the box,
-
-I am happy to tell you that we have, and we are constantly adding more possible combinations,
-
-so you are more than welcome to tell us what combinations you expect.
-
-- [GitOps Toolchain](https://docs.devstream.io/en/latest/best-practices/gitops/)
-- [GitLab, Jenkins and Harbor On Premise Toolchain (Chinese only for now)](https://docs.devstream.io/en/latest/best-practices/gitlab-jenkins-harbor-java-springboot.zh/)
-
-## Supported DevOps Tools
-
-DevStream already supports many tools and it's still growing. For a complete list of supported tools, check out our [list of plugins](https://docs.devstream.io/en/latest/plugins/plugins-list/) document.
-
-Alternatively, run `dtm list plugins` and it will show you all the available plugins.
-
-## Dev Info
-
-### Pre-requisites
-
-- Git
-- Go (1.18+)
-
-### Development Guide
-
-- [Development Environment Setup](https://docs.devstream.io/en/latest/development/dev/dev-env-setup)
-- [Code linter](https://docs.devstream.io/en/latest/development/dev/lint)
-- [Build the source code](https://docs.devstream.io/en/latest/development/dev/build)
-- [Test the source code: unit test, e2e test](https://docs.devstream.io/en/latest/development/dev/test)
-- [Create a plugin](https://docs.devstream.io/en/latest/development/dev/creating-a-plugin)
-
-## Contribute
-
-First of all, thanks for wanting to contribute to DevStream! For more details on how to contribute, contributor growth program, style guide and more, please check out our [CONTRIBUTING](./CONTRIBUTING.md) document.
-
-## Community
-
-We will regularly organize `DevStream Community Meeting`, please visit the [wiki](https://github.com/devstream-io/devstream/wiki) page for details.
-
-Please join our Slack channel. Here's how:
-
-1. [Invite yourself to CNCF's Slack if you haven't done so](https://slack.cncf.io).
- - Input your email address, and click "get my invite."
- - Open your inbox, find the invitation email, and click "join now."
- - You can join by Email or with your Google account; follow the instructions.
-2. Join DevStream channel, there are two ways to do so:
- - Use [this link](https://cloud-native.slack.com/messages/devstream) to join the channel.
- - In your Slack app, on the left side navigation bar, move your mouse to the "Channels" section, and there should emerge a "plus" sign on the right. Click, and select "browse channels." Input "devstream", and join.
-3. For Mandarin-speaking users and contributors, you are also encouraged to join the [devstream-mandarin](https://cloud-native.slack.com/messages/devstream-mandarin) channel, where all discussions will be in Mandarin.
-
-For WeChat users, you can also join our WeChat group:
-
-
-
-## Code of Conduct
-
-[DevStream code of conduct](./CODE_OF_CONDUCT.md)
-
-As of Jun 2022, we joined CNCF sandbox. We also need to follow the [CNCF Community Code of Conduct](https://github.com/cncf/foundation/blob/main/code-of-conduct.md).
+to be updated
diff --git a/README_zh.md b/README_zh.md
deleted file mode 100644
index 9e112c151..000000000
--- a/README_zh.md
+++ /dev/null
@@ -1,147 +0,0 @@
-- -
-
# DevStream
-[](https://makeapullrequest.com)
-
-[](https://goreportcard.com/report/github.com/devstream-io/devstream)
-[](https://github.com/devstream-io/devstream/releases)
-[](https://bestpractices.coreinfrastructure.org/projects/6202)
-[](https://cloud-native.slack.com/archives/C03LA2B8K0A)
-
-| English | [中文](README_zh.md) |
-| --- | --- |
-
-
-
- -
-
-# DevStream
-
-[](https://makeapullrequest.com)
-
-[](https://goreportcard.com/report/github.com/devstream-io/devstream)
-[](https://bestpractices.coreinfrastructure.org/projects/6202)
-[](https://github.com/devstream-io/devstream/releases)
-[](https://cloud-native.slack.com/archives/C03LA2B8K0A)
-
-| [English](README.md) | 中文 |
-| --- | --- |
-
-
-
-## DevStream 是什么？
-TL;DR: DevStream（CLI工具名为`dtm`）是一个开源的DevOps工具链管理器。
-
-[v0.6.0 Demo](https://www.bilibili.com/video/BV1W3411P7oW/)
-
-想象你正在开始一个新的项目或组建一个新的团队。在写第一行代码之前，你需要一个能够高效运转SDLC(软件开发生命周期)和承载开发至部署全过程的工具。
-
-通常情况下，你需要以下几个部分来高效地工作。
-
-- 项目管理软件或 `issue` 追溯工具（JIRA等）
-- 源代码管理（GitHub、Bitbucket等）
-- 持续集成（Jenkins、CircleCI、Travis CI等）
-- 持续交付/部署（Flux CD/Flux2、Argo CD等)
-- 密钥和证书的单一事实来源(A single source of truth)（密钥管理器，如HashiCorp的Vault）
-- 集成化的日志和监控工具（例如，ELK、Prometheus/Grafana）
-- ......
-
-具体内容远远不止这些，不过你应该已经明白意思了。
-
-在创建一个高效、定制化的工作流上，当前有许多挑战。
-
-- 我们有很多选择。哪个是最好的？没有"放之四海而皆准"的答案，因为这完全取决于你的需求和喜好。
-- 不同部分之间的整合是非常具有挑战性的，否则将导致项目孤岛化、碎片化。
-- 软件领域演进很快。今天最好的东西可能明天就毫无意义。如果你想换掉一些组件或工具，管理起来会很困难，也很耗费资源。
-
-说实话，有一些产品可能包含你需要的一切，但它们可能并不完全适合你的具体要求。因此，你仍然需要自己去搜寻，找到最好的组件，并自己将它们整合起来。也就是说，选择、启动、连接和管理所有这些组件需要大量的时间和精力。
-
-你可能已经看到了我们想要做的事情......
-
-我们想简化整合组件的过程，所以我们建立了DevStream，一个开源的DevOps工具链管理器。
-
-想一想Linux内核与不同发行版的关系。不同的发行版提供不同的软件包，这样你就可以随时选择你最需要的。
-
-或者，想想`yum`、`apt`或`apk`。你可以使用这些包管理器为任何新环境轻松设置你最喜欢的软件包。
-
-**DevStream的目标是成为DevOps工具的软件包管理器。**
-
-**更具野心的是，DevStream想成为Linux内核，你可以用各种组件创建不同的发行版，为SDLC工作流的每个部分选择最适合的组件。**
-
-## 为什么是 `dtm` ？
-Q：CLI被命名为 `dtm`，而工具本身被称为 `DevStream`。这是怎么回事！？一致性在哪里？
-
-A：受 [`git`](https://github.com/git/git#readme) 的启发，这个名字可以是（取决于你的心情）：
-
-- "**d**evs**t**rea**m**": 一个对称缩写。
-- "**D**evops **T**oolchain **M**anager"：当它对你有用的时候。
-- "**d**ead **t**o **m**e"：当它崩溃的时候。
-
-## 为什么使用DevStream？
-
-不再需要手动的 `curl/wget` 下载、`apt` 安装、`helm` 安装；不再需要预先的本地试验以保证组件能正确安装。
-
-在一个人类可读的 `YAML` 配置文件中定义你所需要的DevOps工具，只需按一个按钮（或一个命令），你就能建立起整个DevOps工具链和SDLC工作流。
-
-五分钟，一个命令。
-
-想安装另一个不同的工具来试一试？没问题。
-
-想删除或重新安装工作流中的某个特定部分？DevStream已经帮你解决了!
-
-## 快速入门
-
-现在就跟随我们的[快速入门](https://docs.devstream.io/en/latest/quickstart.zh/)文档开始使用 DevStream
-
-## 最佳实践
-
-DevStream支持许多工具的管理。你可以灵活地结合一些工具来满足你所需要的DevOps工具链。
-
-是的，如果你问我是否有可以开箱即用的推荐实践。
-
-我很高兴地告诉你，我们有，而且我们正在不断增加更多可能的组合。
-
-我们非常欢迎你告诉我们你期望的组合。
-
-- [GitOps工具链](https://docs.devstream.io/en/latest/best-practices/gitops.zh/)
-- [用 DevStream 搭建 GitLab + Jenkins + Harbor 工具链，管理 Java Spring Boot 项目开发生命周期全流程](https://docs.devstream.io/en/latest/best-practices/gitlab-jenkins-harbor-java-springboot.zh/)
-
-## 支持的DevOps工具
-
-DevStream已经支持许多工具，而且还在不断增加。关于支持的工具的完整列表，请查看我们的 [插件列表](https://docs.devstream.io/en/latest/plugins/plugins-list) 文档。
-
-或者，运行 `dtm list plugins`，它将显示所有可用的插件。
-
-## 开发指南
-
-### 前提条件
-
-- Git
-- Go (1.18版本以上)
-
-### 开发指南
-
-- [开发环境搭建](https://docs.devstream.io/en/latest/development/dev/dev-env-setup.zh)
-- [代码格式检查](https://docs.devstream.io/en/latest/development/dev/lint.zh)
-- [源码构建](https://docs.devstream.io/en/latest/development/dev/build.zh)
-- [代码测试：单元测试(unit test)、端到端测试(e2e test)](https://docs.devstream.io/en/latest/development/dev/test.zh)
-- [开发新插件](https://docs.devstream.io/en/latest/development/dev/creating-a-plugin.zh)
-
-## 贡献
-
-首先，感谢你愿意为DevStream做贡献！
-
-关于如何贡献、贡献者成长计划、风格指南等更多细节，请查看我们的 [CONTRIBUTING](CONTRIBUTING.md) 文档。
-
-## 社区
-
-我们将定期组织 "DevStream Community Meeting"，请访问 [WIKI](https://github.com/devstream-io/devstream/wiki) 页面了解详情。
-
-另外，请加入我们的Slack channel，请参见如下步骤：
-
-1. [给自己发送进入CNCF的Slack的邀请](https://slack.cncf.io)。
- - 输入邮箱地址，点击"get my invite"。
- - 打开收件箱，找到邀请邮件，点击邮件中的"join now"。
- - 你可以用邮箱地址或者Google账号等方式加入，跟随屏幕提示即可。
-2. 对于会说英文的用户：加入DevStream的英语频道。以下两种方式均可：
- - [点击这里](https://cloud-native.slack.com/messages/devstream)。
- - 在Slack app里，在左侧的导航栏，找到“频道”区域，将鼠标移动到上面，这时“频道”的右侧会出现一个加号。点击加号，然后选择“浏览频道”。输入"devstream"，找到频道然后加入。
-3. 对于只说中文的用户，可以加入[devstream-mandarin](https://cloud-native.slack.com/messages/devstream-mandarin)频道，这里的讨论都是用中文进行的。
-
-对于使用微信的用户，请扫描二维码进群：
-
-
-
-## 行为守则
-
-[DevStream行为守则](/CODE_OF_CONDUCT.md)
-
-DevStream于2022年6月加入CNCF沙盒。我们也需要遵循[云原生计算基金会（CNCF）社区行为准则](https://github.com/cncf/foundation/blob/main/code-of-conduct-languages/zh.md).
diff --git a/ROADMAP.md b/ROADMAP.md
index eb9f5d745..258cd5725 100644
--- a/ROADMAP.md
+++ b/ROADMAP.md
@@ -1,109 +1 @@
-# Roadmap
-
-## 1 New Tools to Support (Plugins)
-
-- artifactory: https://github.com/devstream-io/devstream/issues/607
-- Jenkins pipeline plugin: https://github.com/devstream-io/devstream/issues/582
-- Cloudflare IP List Monitor: https://github.com/devstream-io/devstream/issues/560
-- Use Validator for Config Validation: https://github.com/devstream-io/devstream/issues/558
-- GitLab CE: https://github.com/devstream-io/devstream/issues/509
-- zendao: https://github.com/devstream-io/devstream/issues/508
-- Tekton
-- Jira-GitHub, Jira-GitLab integration
-- Jenkins-GitHub, Jenkins-GitLab integration
-- ArgoCD-GitHub SSO integration
-- Repository bootstrapping for Python/Nodejs for GitHub, Golang/Python/Nodejs for GitLab
-- GitLab CI workflows for Python/Nodejs
-- FluxCD plugin
-- Trello-GitLab Integration
-
-## 2 Core Features
-
-General:
-
-- single config profile support: https://github.com/devstream-io/devstream/issues/596
-- make sure people who don't have optimum internet connections (e.g., users behind firewall or proxy) can still use DevStream smoothly.
-
-### `dtm show config`
-
-This is already supported, but we will improve the features of it, for example:
-
-- show the default configs of multiple plugins that are used together
-- interactive: user select plugin then show the default config
-
-## 3 Quality of Life Improvements for Developers
-
-### Automated End-to-End Testing in a Staging Environment
-
-- AWS EC2 (linux-amd64) creation with Terraform/Ansible
-- Push notification to Slack/Lark when the testing environment is occupied or released
-
-### Misc
-
-- Integrate the golangci-lint command in the makefile https://github.com/devstream-io/devstream/issues/632
-- Push notification when CI failed: https://github.com/devstream-io/devstream/issues/636
-- Shorter CI time: for example, adding packages into a base image
-- More end-to-end tests coverage, to test more typical usecases and plugins
-- Push notification to core committers when there is a new PR ready for review
-
-## 4 Already Done
-
-Core:
-- local state support: https://github.com/devstream-io/devstream/issues/16
-- pluginmanager module: https://github.com/devstream-io/devstream/issues/17
-- statemanager supports concurrent map: https://github.com/devstream-io/devstream/issues/71
-- pluginmanager download status bar: https://github.com/devstream-io/devstream/issues/88, https://github.com/devstream-io/devstream/issues/98
-- multi-plugin instance support: https://github.com/devstream-io/devstream/issues/136
-- force delete feature: https://github.com/devstream-io/devstream/issues/177, https://github.com/devstream-io/devstream/issues/278
-- `verify` command: https://github.com/devstream-io/devstream/issues/252, https://github.com/devstream-io/devstream/issues/253
-- output support: https://github.com/devstream-io/devstream/issues/324
-- Homebrew support: https://github.com/devstream-io/devstream/issues/351, https://github.com/devstream-io/devstream/issues/372
-- remote state: https://github.com/devstream-io/devstream/issues/378, https://github.com/devstream-io/devstream/issues/485
-- autocomplete: https://github.com/devstream-io/devstream/issues/380
-- generate default config: https://github.com/devstream-io/devstream/issues/383
-- list all plugins: https://github.com/devstream-io/devstream/issues/384
-- config supports global variables: https://github.com/devstream-io/devstream/issues/393
-- plugin status: https://github.com/devstream-io/devstream/issues/401
-- parallel download: https://github.com/devstream-io/devstream/issues/579
-- plugins released to AWS S3 instead of GitHub releases page
-
-Plugins:
-- Jenkins plugin: https://github.com/devstream-io/devstream/issues/11
-- GitLab CI plugin: https://github.com/devstream-io/devstream/issues/12
-- GitHub Actions plugin for Nodejs and Python: https://github.com/devstream-io/devstream/issues/14
-- GitHub Actions plugin supports test coverage: https://github.com/devstream-io/devstream/issues/133
-- GitHub repo scaffolding for Golang plugin: https://github.com/devstream-io/devstream/issues/191, https://github.com/devstream-io/devstream/issues/520
-- Prometheus/grafana plugin: https://github.com/devstream-io/devstream/issues/231
-- Helm type plugins support values: https://github.com/devstream-io/devstream/issues/272
-- openldap plugin: https://github.com/devstream-io/devstream/issues/284
-- trello plugin: https://github.com/devstream-io/devstream/issues/307, https://github.com/devstream-io/devstream/issues/314
-- GitLab CI generic plugin: https://github.com/devstream-io/devstream/issues/377
-- Helm generic plugin: https://github.com/devstream-io/devstream/issues/424
-
-Develop:
-- cross-platform build: https://github.com/devstream-io/devstream/issues/21, https://github.com/devstream-io/devstream/issues/170
-- end to end test: https://github.com/devstream-io/devstream/issues/50, https://github.com/devstream-io/devstream/issues/118
-- logging level: https://github.com/devstream-io/devstream/issues/176
-- parallel build: https://github.com/devstream-io/devstream/issues/361
-- automated release: https://github.com/devstream-io/devstream/issues/364
-- command to help contributors to generate scaffolding code: https://github.com/devstream-io/devstream/issues/454, https://github.com/devstream-io/devstream/issues/443, https://github.com/devstream-io/devstream/issues/436
-- params validation improvement: https://github.com/devstream-io/devstream/issues/511
-- editor config: https://github.com/devstream-io/devstream/issues/629
-
-By versions:
-
-v0.3.1:
-- automated release: when a new tag is generated, build binaries for different platforms/OS and distribute the binaries to the plugin storage.
-
-v0.3.0:
-- "Destroy" and "force delete": everything can be cleared up without any residue or side effects.
-- "Output": all plugin's output is printed for users to review.
-- Plugin dependency management: a common way to handle plugin dependencies and execution order using graph/topology sort.
-- Automated e2e testing: AWS EKS cluster with Terraform.
-- Trello plugin that creates boards.
-
-v0.4.0-v0.5.0:
-- generic GitLab CI plugin
-- define variables and use it in the config file.
-- auto-complete support for `dtm` commands
-- HashiCorp Vault
+todo
diff --git a/SECURITY.md b/SECURITY.md
index cb7c3d3ed..ab70a6ddd 100644
--- a/SECURITY.md
+++ b/SECURITY.md
@@ -1,6 +1,6 @@
# DevStream Security Policy
-Version: **v0.1 (2022-02-28)**
+Version: **v0.12 (2023-04-24)**
## Overview
@@ -20,7 +20,6 @@ In some cases, where a security fix needs complex re-design of a feature or is o
Please report vulnerabilities by e-mail to the following address:
-- tiexin.guo@merico.dev
- tao.hu@merico.dev
If you find a security-related bug in DevStream, we kindly ask you to disclose responsibly and give us appropriate time to react to mitigate the vulnerability.
diff --git a/cmd/devstream/apply.go b/cmd/devstream/apply.go
deleted file mode 100644
index c1abf3694..000000000
--- a/cmd/devstream/apply.go
+++ /dev/null
@@ -1,39 +0,0 @@
-package main
-
-import (
- "os"
- "strings"
-
- "github.com/spf13/cobra"
-
- "github.com/devstream-io/devstream/internal/pkg/pluginengine"
- "github.com/devstream-io/devstream/pkg/util/log"
-)
-
-var applyCMD = &cobra.Command{
- Use: "apply",
- Short: "Create or update DevOps tools according to DevStream configuration file",
- Long: `Create or update DevOps tools according to DevStream configuration file.
-DevStream will generate and execute a new plan based on the config file and the state file by default.`,
- Run: applyCMDFunc,
- SuggestFor: []string{"install"},
-}
-
-func applyCMDFunc(cmd *cobra.Command, args []string) {
- checkConfigFile()
- log.Info("Apply started.")
- if err := pluginengine.Apply(configFilePath, continueDirectly); err != nil {
- log.Errorf("Apply failed => %s.", err)
- if strings.Contains(err.Error(), "config not valid") {
- log.Info("It seems your config file is not valid. Please check the official documentation https://docs.devstream.io, or use the \"dtm show config\" command to get an example.")
- }
- os.Exit(1)
- }
- log.Success("Apply finished.")
-}
-
-func init() {
- addFlagConfigFile(applyCMD)
- addFlagPluginDir(applyCMD)
- addFlagContinueDirectly(applyCMD)
-}
diff --git a/cmd/devstream/common.go b/cmd/devstream/common.go
deleted file mode 100644
index c6944d415..000000000
--- a/cmd/devstream/common.go
+++ /dev/null
@@ -1,44 +0,0 @@
-package main
-
-import (
- "os"
- "strings"
-
- "github.com/spf13/cobra"
-
- "github.com/devstream-io/devstream/internal/pkg/completion"
- "github.com/devstream-io/devstream/pkg/util/log"
-)
-
-var (
- configFilePath string
- pluginDir string
- continueDirectly bool
-)
-
-const (
- configFlagName = "config-file"
- pluginDirFlagName = "plugin-dir"
- defaultPluginDir = "~/.devstream/plugins"
-)
-
-func checkConfigFile() {
- if strings.TrimSpace(configFilePath) == "" {
- log.Errorf(`Config file is required. You could use "-f filename" or "-f directory" to specify it.`)
- os.Exit(1)
- }
-}
-
-func addFlagConfigFile(cmd *cobra.Command) {
- cmd.Flags().StringVarP(&configFilePath, configFlagName, "f", "", "config file or directory")
- completion.FlagFilenameCompletion(cmd, configFlagName)
-}
-
-func addFlagPluginDir(cmd *cobra.Command) {
- cmd.Flags().StringVarP(&pluginDir, pluginDirFlagName, "d", defaultPluginDir, "plugins directory")
- completion.FlagDirnameCompletion(cmd, pluginDirFlagName)
-}
-
-func addFlagContinueDirectly(cmd *cobra.Command) {
- cmd.Flags().BoolVarP(&continueDirectly, "yes", "y", false, "continue directly without confirmation")
-}
diff --git a/cmd/devstream/completion.go b/cmd/devstream/completion.go
deleted file mode 100644
index c7ea6a49e..000000000
--- a/cmd/devstream/completion.go
+++ /dev/null
@@ -1,64 +0,0 @@
-package main
-
-import (
- "io"
- "os"
- "path/filepath"
-
- "github.com/spf13/cobra"
-
- cobracompletefig "github.com/withfig/autocomplete-tools/integrations/cobra"
-
- "github.com/devstream-io/devstream/internal/pkg/completion"
-)
-
-func completionCMD(out io.Writer) *cobra.Command {
- cmd := &cobra.Command{
- Use: "completion",
- Short: "Generate the autocompletion script for dtm for the specified shell",
- Long: "See each sub-command's help for details on how to use the generated script.",
- DisableFlagsInUseLine: true,
- Args: cobra.ExactValidArgs(1),
- }
-
- binaryName := filepath.Base(os.Args[0])
- bash := &cobra.Command{
- Use: "bash",
- Short: "generate autocompletion script for bash",
- Example: completion.BashExample(binaryName),
- RunE: func(cmd *cobra.Command, args []string) error {
- return completion.CompletionBash(out, cmd)
- },
- }
-
- zsh := &cobra.Command{
- Use: "zsh",
- Short: "generate autocompletion script for zsh",
- Example: completion.ZshExample(binaryName),
- RunE: func(cmd *cobra.Command, args []string) error {
- return completion.CompletionZsh(out, cmd)
- },
- }
-
- fish := &cobra.Command{
- Use: "fish",
- Short: "generate autocompletion script for fish",
- Example: completion.FishExample(binaryName),
- RunE: func(cmd *cobra.Command, args []string) error {
- return cmd.Root().GenFishCompletion(out, true)
- },
- }
-
- powershell := &cobra.Command{
- Use: "powershell",
- Short: "generate autocompletion script for powershell",
- Example: completion.PowershellExample(binaryName),
- RunE: func(cmd *cobra.Command, args []string) error {
- return cmd.Root().GenPowerShellCompletionWithDesc(out)
- },
- }
-
- cmd.AddCommand(bash, zsh, fish, powershell, cobracompletefig.CreateCompletionSpecCommand(cobracompletefig.Opts{Use: "fig"}))
-
- return cmd
-}
diff --git a/cmd/devstream/create.go b/cmd/devstream/create.go
deleted file mode 100644
index 18fc7b5a9..000000000
--- a/cmd/devstream/create.go
+++ /dev/null
@@ -1,23 +0,0 @@
-package main
-
-import (
- "fmt"
-
- "github.com/spf13/cobra"
-
- "github.com/devstream-io/devstream/internal/pkg/create"
-)
-
-var createCMD = &cobra.Command{
- Use: "create",
- Short: "create",
- Long: `create.`,
- Run: createCMDFunc,
-}
-
-func createCMDFunc(cmd *cobra.Command, args []string) {
- err := create.Create()
- if err != nil && err.Error() != "^C" {
- fmt.Printf("Failed with error: %s", err)
- }
-}
diff --git a/cmd/devstream/delete.go b/cmd/devstream/delete.go
deleted file mode 100644
index b2cd65a1c..000000000
--- a/cmd/devstream/delete.go
+++ /dev/null
@@ -1,39 +0,0 @@
-package main
-
-import (
- "os"
-
- "github.com/spf13/cobra"
-
- "github.com/devstream-io/devstream/internal/pkg/pluginengine"
- "github.com/devstream-io/devstream/pkg/util/log"
-)
-
-var isForceDelete bool
-
-var deleteCMD = &cobra.Command{
- Use: "delete",
- Short: "Delete DevOps tools according to DevStream configuration file",
- Long: `Delete DevOps tools according to DevStream configuration file.
-DevStream will delete everything defined in the config file, regardless of the state.`,
- Run: deleteCMDFunc,
-}
-
-func deleteCMDFunc(cmd *cobra.Command, args []string) {
- checkConfigFile()
- log.Info("Delete started.")
- if err := pluginengine.Remove(configFilePath, continueDirectly, isForceDelete); err != nil {
- log.Errorf("Delete error: %s.", err)
- os.Exit(1)
- }
-
- log.Success("Delete finished.")
-}
-
-func init() {
- addFlagConfigFile(deleteCMD)
- addFlagPluginDir(deleteCMD)
- addFlagContinueDirectly(deleteCMD)
-
- deleteCMD.Flags().BoolVarP(&isForceDelete, "force", "", false, "force delete by config")
-}
diff --git a/cmd/devstream/destroy.go b/cmd/devstream/destroy.go
deleted file mode 100644
index f5f5afeb8..000000000
--- a/cmd/devstream/destroy.go
+++ /dev/null
@@ -1,37 +0,0 @@
-package main
-
-import (
- "os"
-
- "github.com/spf13/cobra"
-
- "github.com/devstream-io/devstream/internal/pkg/pluginengine"
- "github.com/devstream-io/devstream/pkg/util/log"
-)
-
-var isForceDestroy bool
-
-var destroyCMD = &cobra.Command{
- Use: "destroy",
- Short: "Destroy DevOps tools deployment according to DevStream configuration file & state file",
- Long: `Destroy DevOps tools deployment according to DevStream configuration file & state file.`,
- Run: destroyCMDFunc,
-}
-
-func destroyCMDFunc(cmd *cobra.Command, args []string) {
- checkConfigFile()
- log.Info("Destroy started.")
- if err := pluginengine.Destroy(configFilePath, continueDirectly, isForceDestroy); err != nil {
- log.Errorf("Destroy failed => %s.", err)
- os.Exit(1)
- }
- log.Success("Destroy finished.")
-}
-
-func init() {
- addFlagConfigFile(destroyCMD)
- addFlagPluginDir(destroyCMD)
- addFlagContinueDirectly(destroyCMD)
-
- destroyCMD.Flags().BoolVarP(&isForceDestroy, "force", "", false, "force destroy by config")
-}
diff --git a/cmd/devstream/develop.go b/cmd/devstream/develop.go
deleted file mode 100644
index 95aeaa5be..000000000
--- a/cmd/devstream/develop.go
+++ /dev/null
@@ -1,66 +0,0 @@
-package main
-
-import (
- "github.com/spf13/cobra"
-
- "github.com/devstream-io/devstream/internal/pkg/develop"
- "github.com/devstream-io/devstream/pkg/util/cli"
- "github.com/devstream-io/devstream/pkg/util/log"
-)
-
-var (
- name string
- all bool
-)
-
-var validatePluginFlagNames = []string{
- "name",
- "all",
-}
-
-var developCMD = &cobra.Command{
- Use: "develop",
- Short: "Develop is used for develop a new plugin",
-}
-
-var developCreatePluginCMD = &cobra.Command{
- Use: "create-plugin",
- Short: "Create a new plugin",
- Long: `Create-plugin is used for creating a new plugin.
-Examples:
- dtm develop create-plugin --name=YOUR-PLUGIN-NAME`,
- Run: developCreateCMDFunc,
-}
-
-var developValidatePluginCMD = &cobra.Command{
- Use: "validate-plugin",
- Short: "Validate a plugin",
- Long: `Validate-plugin is used for validating an existing plugin or all plugins.
-Examples:
- dtm develop validate-plugin --name=YOUR-PLUGIN-NAME,
- dtm develop validate-plugin --all`,
- Run: developValidateCMDFunc,
- PreRun: cli.BindPFlags(validatePluginFlagNames),
-}
-
-func developCreateCMDFunc(cmd *cobra.Command, args []string) {
- if err := develop.CreatePlugin(); err != nil {
- log.Fatal(err)
- }
-}
-
-func developValidateCMDFunc(cmd *cobra.Command, args []string) {
- if err := develop.ValidatePlugin(); err != nil {
- log.Fatal(err)
- }
-}
-
-func init() {
- developCMD.AddCommand(developCreatePluginCMD)
- developCMD.AddCommand(developValidatePluginCMD)
-
- developCreatePluginCMD.PersistentFlags().StringVarP(&name, "name", "n", "", "specify name of the plugin to be created")
-
- developValidatePluginCMD.PersistentFlags().StringVarP(&name, "name", "n", "", "specify name of the plugin to be validated")
- developValidatePluginCMD.PersistentFlags().BoolVarP(&all, "all", "a", false, "validate all plugins")
-}
diff --git a/cmd/devstream/init.go b/cmd/devstream/init.go
deleted file mode 100644
index d5a466f43..000000000
--- a/cmd/devstream/init.go
+++ /dev/null
@@ -1,128 +0,0 @@
-package main
-
-import (
- "errors"
- "fmt"
- "runtime"
- "strings"
-
- "github.com/spf13/cobra"
-
- "github.com/devstream-io/devstream/cmd/devstream/list"
- "github.com/devstream-io/devstream/internal/pkg/configmanager"
- "github.com/devstream-io/devstream/internal/pkg/pluginmanager"
- "github.com/devstream-io/devstream/internal/pkg/version"
- "github.com/devstream-io/devstream/pkg/util/log"
-)
-
-var initCMD = &cobra.Command{
- Use: "init",
- Short: "Download needed plugins according to the config file",
- Long: `Download needed plugins according to the config file`,
- Run: initCMDFunc,
-}
-
-var (
- downloadOnly bool // download plugins only, from command line flags
- downloadAll bool // download all plugins
- pluginsToDownload []string // download specific plugins
- initOS string // download plugins for specific os
- initArch string // download plugins for specific arch
-)
-
-func initCMDFunc(_ *cobra.Command, _ []string) {
- if version.Dev {
- log.Fatalf("Dev version plugins can't be downloaded from the remote plugin repo; please run `make build-plugin.PLUGIN_NAME` to build them locally.")
- }
-
- var (
- tools configmanager.Tools
- err error
- )
-
- if downloadOnly {
- // download plugins from flags
- tools, err = GetPluginsFromFlags()
- } else {
- // download plugins according to the config file
- tools, err = GetPluginsFromConfig()
- }
-
- if err != nil {
- log.Fatal(err)
- }
-
- pluginDir, err = pluginmanager.GetPluginDir()
- if err != nil {
- log.Fatal(err)
- }
- log.Debugf("Plugin directory: %s.", pluginDir)
-
- if err = pluginmanager.DownloadPlugins(tools, pluginDir, initOS, initArch); err != nil {
- log.Fatal(err)
- }
-
- fmt.Println()
- log.Success("Initialize finished.")
-}
-
-func GetPluginsFromConfig() (tools configmanager.Tools, err error) {
- cfg, err := configmanager.NewManager(configFilePath).LoadConfig()
- if err != nil {
- return nil, err
- }
-
- return cfg.Tools, nil
-}
-
-func GetPluginsFromFlags() (tools configmanager.Tools, err error) {
- // 1. get plugins from flags
- var pluginsName []string
- if downloadAll {
- // download all plugins
- pluginsName = list.PluginsNameSlice()
- } else {
- // download specific plugins
- for _, pluginName := range pluginsToDownload {
- if p := strings.ToLower(strings.TrimSpace(pluginName)); p != "" {
- pluginsName = append(pluginsName, p)
- }
- }
- // check if plugins to download are supported by dtm
- for _, plugin := range pluginsName {
- if _, ok := list.PluginNamesMap()[plugin]; !ok {
- return nil, fmt.Errorf("plugin %s is not supported by dtm", plugin)
- }
- }
- }
-
- if len(pluginsName) == 0 {
- return nil, errors.New("please use --plugins to specify plugins to download or use --all to download all plugins")
- }
- log.Debugf("plugins to download: %v", pluginsName)
-
- if initOS == "" || initArch == "" {
- return nil, fmt.Errorf("once you use the --all flag, you must specify the --os and --arch flags")
- }
-
- log.Infof("Plugins to download: %v", pluginsName)
-
- // build the plugin list
- for _, pluginName := range pluginsName {
- tools = append(tools, &configmanager.Tool{Name: pluginName})
- }
-
- return tools, nil
-}
-
-func init() {
- addFlagConfigFile(initCMD)
- addFlagPluginDir(initCMD)
-
- // downloading specific plugins from flags
- initCMD.Flags().BoolVar(&downloadOnly, "download-only", false, "download plugins only")
- initCMD.Flags().StringSliceVarP(&pluginsToDownload, "plugins", "p", []string{}, "the plugins to be downloaded")
- initCMD.Flags().BoolVarP(&downloadAll, "all", "a", false, "download all plugins")
- initCMD.Flags().StringVar(&initOS, "os", runtime.GOOS, "download plugins for specific os")
- initCMD.Flags().StringVar(&initArch, "arch", runtime.GOARCH, "download plugins for specific arch")
-}
diff --git a/cmd/devstream/list.go b/cmd/devstream/list.go
deleted file mode 100644
index ca0b92145..000000000
--- a/cmd/devstream/list.go
+++ /dev/null
@@ -1,39 +0,0 @@
-package main
-
-import (
- "github.com/spf13/cobra"
-
- "github.com/devstream-io/devstream/cmd/devstream/list"
-)
-
-var (
- pluginFilter string
-)
-
-var listCMD = &cobra.Command{
- Use: "list",
- Short: "This command only supports listing plugins now",
-}
-
-var listPluginsCMD = &cobra.Command{
- Use: "plugins",
- Short: "List all plugins",
- Long: `This command lists all of the plugins.
-Examples:
- dtm list plugins
- dtm list plugins --filter=argo.*
- dtm list plugins -r ^argo
-`,
- Run: listPluginsCMDFunc,
-}
-
-func listPluginsCMDFunc(_ *cobra.Command, _ []string) {
- list.List(pluginFilter)
-}
-
-// TODO Use `--group=somegroup` to filter the specified groups on feature
-func init() {
- listCMD.AddCommand(listPluginsCMD)
-
- listPluginsCMD.PersistentFlags().StringVarP(&pluginFilter, "filter", "r", "", "filter plugin by regex")
-}
diff --git a/cmd/devstream/list/list.go b/cmd/devstream/list/list.go
deleted file mode 100644
index c75a999c2..000000000
--- a/cmd/devstream/list/list.go
+++ /dev/null
@@ -1,45 +0,0 @@
-package list
-
-import (
- "fmt"
- "regexp"
- "sort"
- "strings"
-)
-
-// list is the version of DevStream.
-// Assign the value when building with the -X parameter. Example:
-// -X github.com/devstream-io/devstream/cmd/devstream/list.PluginsName=${PLUGINS_NAME}
-// See the Makefile for more info.
-
-var PluginsName string
-
-// List all plugins name
-func List(pluginFilter string) {
- r, _ := regexp.Compile(pluginFilter)
- for _, pluginName := range PluginsNameSlice() {
- if r.Match([]byte(pluginName)) {
- fmt.Println(pluginName)
- }
- }
-}
-
-// PluginsNameSlice Gets plugins name in slice
-func PluginsNameSlice() []string {
- listPluginsName := strings.Fields(PluginsName)
- sort.Strings(listPluginsName)
- return listPluginsName
-}
-
-// PluginNamesMap Gets plugins name in map
-func PluginNamesMap() map[string]struct{} {
- mp := make(map[string]struct{})
-
- listPluginsName := strings.Fields(PluginsName)
-
- for _, pluginName := range listPluginsName {
- mp[pluginName] = struct{}{}
- }
-
- return mp
-}
diff --git a/cmd/devstream/main.go b/cmd/devstream/main.go
deleted file mode 100644
index ffea2e158..000000000
--- a/cmd/devstream/main.go
+++ /dev/null
@@ -1,108 +0,0 @@
-package main
-
-import (
- "os"
-
- "github.com/sirupsen/logrus"
- "github.com/spf13/cobra"
- "github.com/spf13/viper"
-
- "github.com/devstream-io/devstream/pkg/util/log"
-)
-
-var (
- isDebug bool
- rootCMD = &cobra.Command{
- Use: "dtm",
- Short: `DevStream is an open-source DevOps toolchain manager`,
- Long: `DevStream is an open-source DevOps toolchain manager
-
-###### #####
-# # ###### # # # # ##### ##### ###### ## # #
-# # # # # # # # # # # # ## ##
-# # ##### # # ##### # # # ##### # # # ## #
-# # # # # # # ##### # ###### # #
-# # # # # # # # # # # # # # #
-###### ###### ## ##### # # # ###### # # # #
-`,
- PersistentPreRun: func(cmd *cobra.Command, args []string) {
- initLog()
- },
- }
-)
-
-func init() {
- cobra.OnInitialize(initConfig)
- rootCMD.PersistentFlags().BoolVarP(&isDebug, "debug", "", false, "debug level log")
- rootCMD.AddCommand(completionCMD(os.Stdout))
- rootCMD.AddCommand(versionCMD)
- rootCMD.AddCommand(initCMD)
- rootCMD.AddCommand(applyCMD)
- rootCMD.AddCommand(deleteCMD)
- rootCMD.AddCommand(destroyCMD)
- rootCMD.AddCommand(verifyCMD)
- rootCMD.AddCommand(developCMD)
- rootCMD.AddCommand(listCMD)
- rootCMD.AddCommand(showCMD)
- rootCMD.AddCommand(upgradeCMD)
-
- rootCMD.AddCommand(startCMD)
- rootCMD.AddCommand(createCMD)
-}
-
-func initConfig() {
- viper.AutomaticEnv()
- if err := viper.BindEnv("github_token"); err != nil {
- log.Fatal(err)
- }
- if err := viper.BindEnv("kubeconfig"); err != nil {
- log.Fatal(err)
- }
- if err := viper.BindEnv("dockerhub_username"); err != nil {
- log.Fatal(err)
- }
- if err := viper.BindEnv("dockerhub_token"); err != nil {
- log.Fatal(err)
- }
- if err := viper.BindEnv("trello_api_key"); err != nil {
- log.Fatal(err)
- }
- if err := viper.BindEnv("trello_token"); err != nil {
- log.Fatal(err)
- }
- if err := viper.BindPFlags(rootCMD.Flags()); err != nil {
- log.Fatal(err)
- }
- if err := viper.BindPFlags(developCreatePluginCMD.Flags()); err != nil {
- log.Fatal(err)
- }
- if err := viper.BindPFlags(developValidatePluginCMD.Flags()); err != nil {
- log.Fatal(err)
- }
- if err := viper.BindPFlags(showConfigCMD.Flags()); err != nil {
- log.Fatal(err)
- }
- if err := viper.BindPFlags(showStatusCMD.Flags()); err != nil {
- log.Fatal(err)
- }
- if err := viper.BindPFlags(initCMD.Flags()); err != nil {
- log.Fatal(err)
- }
-}
-
-func initLog() {
- if isDebug {
- logrus.SetLevel(logrus.DebugLevel)
- log.Infof("Log level is: %s.", logrus.GetLevel())
- } else {
- logrus.SetLevel(logrus.InfoLevel)
- }
-}
-
-func main() {
-
- err := rootCMD.Execute()
- if err != nil {
- os.Exit(1)
- }
-}
diff --git a/cmd/devstream/show.go b/cmd/devstream/show.go
deleted file mode 100644
index 0ef7e4851..000000000
--- a/cmd/devstream/show.go
+++ /dev/null
@@ -1,74 +0,0 @@
-package main
-
-import (
- "github.com/spf13/cobra"
-
- "github.com/devstream-io/devstream/internal/pkg/completion"
- "github.com/devstream-io/devstream/internal/pkg/show/config"
- "github.com/devstream-io/devstream/internal/pkg/show/status"
- "github.com/devstream-io/devstream/pkg/util/log"
-)
-
-var plugin string
-var instanceID string
-var statusAllFlag bool
-var template string
-
-var showCMD = &cobra.Command{
- Use: "show",
- Short: "Show is used to print plugins' configuration templates or status",
-}
-
-var showConfigCMD = &cobra.Command{
- Use: "config",
- Short: "Show configuration information",
- Long: `Show config is used for showing plugins' template configuration information.
-Examples:
- dtm show config --plugin=A-PLUGIN-NAME,
- dtm show config --template=quickstart,
- dtm show config --template=gitops,
- dtm show config --template=apps`,
- Run: showConfigCMDFunc,
-}
-
-var showStatusCMD = &cobra.Command{
- Use: "status",
- Short: "Show status information",
- Long: `Show status is used for showing plugins' status information.
-Examples:
- dtm show status --plugin=A-PLUGIN-NAME --id=A-PLUGIN-INSTANCE-ID
- dtm show status -p=A-PLUGIN-NAME -i=INSTANCE-ID
- dtm show status --all
- dtm show status -a`,
- Run: showStatusCMDFunc,
-}
-
-func showConfigCMDFunc(_ *cobra.Command, _ []string) {
- log.Debug("Show configuration information.")
- if err := config.Show(); err != nil {
- log.Fatal(err)
- }
-}
-
-func showStatusCMDFunc(_ *cobra.Command, _ []string) {
- log.Debug("Show status information.")
- if err := status.Show(configFilePath); err != nil {
- log.Fatal(err)
- }
-}
-
-func init() {
- showCMD.AddCommand(showConfigCMD)
- showCMD.AddCommand(showStatusCMD)
-
- addFlagConfigFile(showConfigCMD)
- addFlagPluginDir(showConfigCMD)
-
- showConfigCMD.Flags().StringVarP(&plugin, "plugin", "p", "", "specify name with the plugin")
- showConfigCMD.Flags().StringVarP(&template, "template", "t", "", "print a template config, e.g. quickstart/gitops/...")
- completion.FlagPluginsCompletion(showConfigCMD, "plugin")
-
- showStatusCMD.Flags().StringVarP(&plugin, "plugin", "p", "", "specify name with the plugin")
- showStatusCMD.Flags().StringVarP(&instanceID, "id", "i", "", "specify id with the plugin instance")
- showStatusCMD.Flags().BoolVarP(&statusAllFlag, "all", "a", false, "show all instances of all plugins status")
-}
diff --git a/cmd/devstream/start.go b/cmd/devstream/start.go
deleted file mode 100644
index ab2213967..000000000
--- a/cmd/devstream/start.go
+++ /dev/null
@@ -1,23 +0,0 @@
-package main
-
-import (
- "fmt"
-
- "github.com/spf13/cobra"
-
- "github.com/devstream-io/devstream/internal/pkg/start"
-)
-
-var startCMD = &cobra.Command{
- Use: "start",
- Short: "start",
- Long: `start.`,
- Run: startCMDFunc,
-}
-
-func startCMDFunc(_ *cobra.Command, _ []string) {
- err := start.Start()
- if err != nil && err.Error() != "^C" {
- fmt.Printf("Failed with error: %s", err)
- }
-}
diff --git a/cmd/devstream/upgrade.go b/cmd/devstream/upgrade.go
deleted file mode 100644
index 2302ffdd3..000000000
--- a/cmd/devstream/upgrade.go
+++ /dev/null
@@ -1,25 +0,0 @@
-package main
-
-import (
- "github.com/spf13/cobra"
-
- "github.com/devstream-io/devstream/internal/pkg/upgrade"
- "github.com/devstream-io/devstream/pkg/util/log"
-)
-
-var upgradeCMD = &cobra.Command{
- Use: "upgrade",
- Short: "Upgrade dtm to the latest release version",
- Long: `Upgrade dtm to the latest release version.`,
- Run: upgradeCMDFunc,
-}
-
-func upgradeCMDFunc(cmd *cobra.Command, args []string) {
- if err := upgrade.Upgrade(continueDirectly); err != nil {
- log.Fatal(err)
- }
-}
-
-func init() {
- addFlagContinueDirectly(upgradeCMD)
-}
diff --git a/cmd/devstream/verify.go b/cmd/devstream/verify.go
deleted file mode 100644
index e86e67756..000000000
--- a/cmd/devstream/verify.go
+++ /dev/null
@@ -1,29 +0,0 @@
-package main
-
-import (
- "github.com/spf13/cobra"
-
- "github.com/devstream-io/devstream/internal/pkg/pluginengine"
- "github.com/devstream-io/devstream/pkg/util/log"
-)
-
-var verifyCMD = &cobra.Command{
- Use: "verify",
- Short: "Verify DevOps tools according to DevStream config file and state",
- Long: `Verify DevOps tools according to DevStream config file and state.`,
- Run: verifyCMDFunc,
-}
-
-func verifyCMDFunc(cmd *cobra.Command, args []string) {
- log.Info("Verify started.")
- if pluginengine.Verify(configFilePath) {
- log.Success("Verify succeeded.")
- } else {
- log.Info("Verify finished.")
- }
-}
-
-func init() {
- addFlagConfigFile(verifyCMD)
- addFlagPluginDir(verifyCMD)
-}
diff --git a/cmd/devstream/version.go b/cmd/devstream/version.go
deleted file mode 100644
index ecdaf99c6..000000000
--- a/cmd/devstream/version.go
+++ /dev/null
@@ -1,20 +0,0 @@
-package main
-
-import (
- "fmt"
-
- "github.com/spf13/cobra"
-
- "github.com/devstream-io/devstream/internal/pkg/version"
-)
-
-var versionCMD = &cobra.Command{
- Use: "version",
- Short: "Print the version number of DevStream",
- Long: `All software has versions. This is DevStream's`,
- Run: versionCMDFunc,
-}
-
-func versionCMDFunc(cmd *cobra.Command, args []string) {
- fmt.Println(version.Version)
-}
diff --git a/cmd/github.go b/cmd/github.go
new file mode 100644
index 000000000..4c1c64d52
--- /dev/null
+++ b/cmd/github.go
@@ -0,0 +1,22 @@
+package cmd
+
+import (
+ "github.com/spf13/cobra"
+
+ "github.com/devstream-io/devstream/internal/pkg/github"
+)
+
+// githubCmd represents the github command
+var githubCmd = &cobra.Command{
+ Use: "github",
+ Short: "github is used to execute github operations",
+ Long: `github is used to execute github operations
+ 参考 gh`,
+ Run: func(cmd *cobra.Command, args []string) {
+ github.Run()
+ },
+}
+
+func init() {
+ rootCmd.AddCommand(githubCmd)
+}
diff --git a/cmd/patch.go b/cmd/patch.go
new file mode 100644
index 000000000..ac11ec684
--- /dev/null
+++ b/cmd/patch.go
@@ -0,0 +1,49 @@
+/*
+Copyright © 2023 NAME HERE - -
-
-# DevStream
-
-[](https://makeapullrequest.com)
-
-[](https://goreportcard.com/report/github.com/devstream-io/devstream)
-[](https://bestpractices.coreinfrastructure.org/projects/6202)
-[](https://github.com/devstream-io/devstream/releases)
-[](https://cloud-native.slack.com/archives/C03LA2B8K0A)
-
-| [English](README.md) | 中文 |
-| --- | --- |
-
-You are viewing the latest of DevStream docs. Maybe you want to choose a specific version.
"
- var bannerHeight = document.getElementById('announce-msg').offsetHeight + margin
- document.querySelector("header.md-header").style.top = bannerHeight + "px";
- document.querySelector('style').textContent +=
- "@media screen and (min-width: 76.25em){ .md-sidebar { height: 0; top:" + (bannerHeight + headerHeight) + "px !important; }}"
- document.querySelector('style').textContent +=
- "@media screen and (min-width: 60em){ .md-sidebar--secondary { height: 0; top:" + (bannerHeight + headerHeight) + "px !important; }}"
- }
- // at the moment we do not have stable version; keep the following code for future reference
- // else if (rtdData.version !== "stable") {
- // document.querySelector("div[data-md-component=announce]").innerHTML = "You are viewing the docs for a previous version of DevStream, click here to go to the latest stable version.
"
- // var bannerHeight = document.getElementById('announce-msg').offsetHeight + margin
- // document.querySelector("header.md-header").style.top = bannerHeight +"px";
- // document.querySelector('style').textContent +=
- // "@media screen and (min-width: 76.25em){ .md-sidebar { height: 0; top:"+ (bannerHeight+headerHeight)+"px !important; }}"
- // document.querySelector('style').textContent +=
- // "@media screen and (min-width: 60em){ .md-sidebar--secondary { height: 0; top:"+ (bannerHeight+headerHeight)+"px !important; }}"
- // }
-});
diff --git a/docs/commands/apply.md b/docs/commands/apply.md
deleted file mode 100644
index 9977246e1..000000000
--- a/docs/commands/apply.md
+++ /dev/null
@@ -1,29 +0,0 @@
-# dtm apply
-
-When _applying_ a config file using `dtm`, here's what happens:
-
-## 1 For Each _Tool_ Defined in the _Config_
-
-We compare the _Tool_, its _State_, and the _Resoruce_ it has created before (if the state exists).
-
-We generate a plan of changes according to the comparison result:
-
-- If the _Tool_ isn't in the _State_, the `Create` interface will be called.
-- If the _Tool_ is in the _State_, but the _Config_ is different than the _State_ (meaning users probably updated the config after the last `apply`,) the `Update` interface will be called.
-- If the _Tool_ is in the _State_, and the _Config_ is the same as the _State_, we try to read the _Resource_.
- - If the _Resource_ doesn't exist, the `Create` interface will be called. It probably suggests that the _Resource_ got deleted manually after the last successful `apply`.
- - If the _Resource_ does exist but drifted from the _State_ (meaning somebody modified it), the `Update` interface will be called.
- - Last but not least, nothing would happen if the _Resource_ is exactly the same as the _State_.
-
-## 2 For Each _State_ That Doesn't Have a _Tool_ in the _Config_
-
-We generate a "Delete" change to delete the _Resource_. Since there isn't a _Tool_ in the config but there is a _State_, it means maybe the _Resource_ had been created previously then the user removed the _Tool_ from the _Config_, which means the user doesn't want the _Resource_ any more.
-
-## 3 Flags
-
-| Short | Long | Default | Description |
-|-------|---------------|--------------------------|--------------------------------------|
-| -f | --config-file | `"config.yaml"` | The path to the config file. |
-| -d | --plugin-dir | `"~/.devstream/plugins"` | The path to store plugins. |
-| -y | --yes | `false` | Apply directly without confirmation. |
-
diff --git a/docs/commands/apply.zh.md b/docs/commands/apply.zh.md
deleted file mode 100644
index 30ba51d53..000000000
--- a/docs/commands/apply.zh.md
+++ /dev/null
@@ -1,28 +0,0 @@
-# dtm apply
-
-当使用 `dtm` _apply_ 配置文件时，会发生以下事情：
-
-## 1 对于 _Config（配置文件）_ 中定义的每个 _Tool_
-
-我们将会对比 _Tool_、它的 _State_ 和它之前创建的 _Resoruce_（如果存在 state）。
-
-根据对比结果，变更规则如下：
-
-- 若该 _Tool_ 不在 _State_ 中，调用 `Create` 接口；
-- 若该 _Tool_ 存在于 _State_ 中，但当前 _Config_ 中关于该 _Tool_ 的配置与 _State_ 中的定义不同（意味着用户可能在上一次 `apply` 之后更新了配置），则调用 `Update` 接口；
-- 若该 _Tool_ 存在于 _State_ 中，且当前 _Config_ 中关于该 _Tool_ 的配置与 _State_ 相同。我们将会继续尝试通过 `Read` 接口读取 _Resource_ ，并与 _State_ 中记录的 _Resource_ 比对：
- - 若从 `Read` 读取到的 _Resource_ 不存在，调用 `Create` 接口。这可能表明 _Resource_ 在最后一次成功 `apply` 后被手动删除；
- - 若从 `Read` 读取到的 _Resource_ 存在，但与 _State_ 中记录的 _Resource_ 不一致（意味着有人修改了 _State_ 或插件状态发生了变化），调用 `Update` 接口；
- - 最后，若读取到的 _Resource_ 和 _State_ 中的 _Resource_ 一致，什么都不做。
-
-## 2 _State_ 中含有某 _Tool_，但 _Config_ 中没有
-
-我们将对其执行"删除"操作，以删除相应的 _Resource_ 。因为 _State_ 中含有此 _Tool_，但配置文件中不存在了，这意味着用户先前为该 _Tool_，创建了 _Resource_，但后面从 _Config_ 中删除了该 _Tool_，表明用户不想要该 _Resource_ 了。
-
-## 3 命令行参数
-
-| 短 | 长 | 默认值 | 描述 |
-|-----|---------------|--------------------------|------------|
-| -f | --config-file | `"config.yaml"` | 配置文件路径 |
-| -d | --plugin-dir | `"~/.devstream/plugins"` | 插件目录 |
-| -y | --yes | `false` | 取消二次确认 |
diff --git a/docs/commands/autocomplete.md b/docs/commands/autocomplete.md
deleted file mode 100644
index 43719dbf4..000000000
--- a/docs/commands/autocomplete.md
+++ /dev/null
@@ -1,136 +0,0 @@
-# Autocomplete
-
-## Fig Autocomplete
-
-In order to give a better experience for terminal users, we [support the Fig Auto-complete](https://github.com/withfig/autocomplete/blob/master/src/dtm.ts).
-
-Unlike other auto-complete tools, [Fig](https://fig.io) is more intuitive. It brings an IDE-style experience to the terminal users. Detailed introduction see the [official website](https://fig.io/)
-
-
-
-**Notice: Temporary only supports MacOS now!**
-
-### Setup
-
-See [https://fig.io](https://fig.io)
-
-
-
-Once the installation is complete, you need to integrate the terminal you are using.
-
-### Examples
-
-#### Get Specified Plugin Information
-
-
-
-#### Get Subcommand Help Information
-
-
-
-#### Build a Specified Plugin
-
-
-
-## Shell Autocomplete
-
-### Bash Autocompletion
-
-#### On Linux
-
-**Note: Main reference [Install and Set Up kubectl on Linux](https://kubernetes.io/docs/tasks/tools/install-kubectl-linux/#enable-shell-autocompletion)**
-
-The completion script depends on `bash-completion`, So you have to install it first.
-
-```bash
-apt-get install bash-completion # For Ubuntu
-
-yum install bash-completion # For CentOS and RedHat
-```
-
-The above commands create `/usr/share/bash-completion/bash_completion`, which is the main script of `bash-completion`. Depending on your package manager, you have to manually source this file in your `~/.bashrc` file.
-
-To find out, reload your shell and run `type _init_completion`. If the command succeeds, you're already set, otherwise add the following to your `~/.bashrc` file:
-
-```bash
-source /usr/share/bash-completion/bash_completion
-```
-
-Reload your shell and verify that bash-completion is correctly installed by typing `type _init_completion`.
-
-Then You can generate completion script for Bash with the command `dtm completion bash` and add the following line to your `~/.bashrc` file. You can execute the following command to add it automatically.
-
-```bash
-echo 'source <(dtm completion bash)' >>~/.bashrc
-source ~/.bashrc
-```
-
-After reloading your shell, dtm autocompletion should be working!
-#### On MacOS
-
-```{admonition} Note
-:class: note
-Main reference [Install and Set Up kubectl on macOS](https://kubernetes.io/docs/tasks/tools/install-kubectl-macos/#enable-shell-autocompletion)
-```
-
-The completion script depends on `bash-completion`, So you have to install it first.
-
-```bash
-brew install bash-completion@2
-```
-
-As stated in the output of this command, add the following to your `~/.bash_profile` file:
-
-```bash
-brew_etc="$(brew --prefix)/etc"
-echo "[[ -r \"${brew_etc}/profile.d/bash_completion.sh\" ]] && . \"${brew_etc}/profile.d/bash_completion.sh\"" >>~/.bash_profile
-source ~/.bash_profile
-```
-
-Reload your shell and verify that bash-completion v2 is correctly installed with `type _init_completion`.
-
-Then You can generate completion script for Bash with the command `dtm completion bash` and add the following to your `~/.bash_profile` file. You can execute the following command to add it automatically.
-
-```bash
-echo 'source <(dtm completion bash)' >>~/.bash_profile
-```
-
-After reloading your shell, dtm autocompletion should be working!
-
-### Zsh Autocompletion
-
-You can generate completion script for Zsh with the command `dtm completion zsh`. Then add the following line to your `~/.zshrc` file. You can execute the following command to add it automatically.
-
-```zsh
-echo 'source <(dtm completion zsh)' >>~/.zshrc
-```
-
-After reloading your shell, dtm autocompletion should be working!
-
-### Fish Autocompletion
-
-You can generate completion script for Fish with the command `dtm completion fish`.Then add the following line to your `~/.config/fish/config.fish` file:
-
-```fish
-dtm completion fish | source
-```
-
-After reloading your shell, dtm autocompletion should be working!
-
-### PowerShell Autocompletion
-
-You can generate completion script for PowerShell with the command `dtm completion powershell`. Then add the following line to your `$PROFILE` file:
-
-```powershell
-dtm completion powershell | Out-String | Invoke-Expression
-```
-
-This command will regenerate the auto-completion script on every PowerShell start up. You can also add the generated script directly to your `$PROFILE` file.
-
-To add the generated script to your `$PROFILE` file, run the following line in your powershell prompt:
-
-```powershell
-dtm completion powershell >> $PROFILE
-```
-
-After reloading your shell, dtm autocompletion should be working.
diff --git a/docs/commands/autocomplete.zh.md b/docs/commands/autocomplete.zh.md
deleted file mode 100644
index 225c4ce22..000000000
--- a/docs/commands/autocomplete.zh.md
+++ /dev/null
@@ -1,139 +0,0 @@
-# 自动补全
-
-## Fig 自动补全
-
-为了给终端用户提供更好的体验，我们支持[Fig 自动补全](https://github.com/withfig/autocomplete/blob/master/src/dtm.ts)。
-
-与其他自动补全工具不同，[Fig](https://fig.io) 更直观。它为终端用户带来了 IDE 风格的体验。详细介绍见[官方网站](https://fig.io/)
-
-
-
-**注意：Fig 目前仅支持 MacOS！**
-
-### 安装 Fig
-
-详见 [https://fig.io](https://fig.io)
-
-
-
-安装完成后，你需要将 Fig 集成到你正在使用的终端。
-
-### 补全示例
-
-#### 查看插件模板配置时，补全插件名
-
-
-
-#### 提示子命令
-
-
-
-#### 构建时，补全插件名
-
-
-
-## Shell 自动补全
-
-### Bash 自动补全
-
-#### Linux
-
-**注：主要参考了 [Install and Set Up kubectl on Linux](https://kubernetes.io/docs/tasks/tools/install-kubectl-linux/#enable-shell-autocompletion)**
-
-自动补全脚本依赖于 `bash-completion`, 需要提前安装：
-
-```bash
-apt-get install bash-completion # Ubuntu
-
-yum install bash-completion # CentOS 和 RedHat
-```
-
-上面的命令会创建 `/usr/share/bash-completion/bash_completion`，这是 `bash-completion` 的主要脚本。取决于不同的包管理器，你需要手动在 `~/.bashrc` 中引入(`source`) 这个文件。
-
-为了测试是否配置成功，请重新加载 shell ，并运行 `type _init_completion` 来确认。若命令执行成功，则配置正确，否则请在 `~/.bashrc` 中添加如下内容：
-
-```bash
-source /usr/share/bash-completion/bash_completion
-```
-
-重新加载 shell ，并运行 `type _init_completion` 来确认是否安装、配置成功。
-
-然后，你可以通过 `dtm completion bash` 命令生成 Bash 自动补全脚本，执行下述命令，以将相应内容添加到 `~/.bashrc` 中：
-
-```bash
-echo 'source <(dtm completion bash)' >>~/.bashrc
-source ~/.bashrc
-```
-
-在重新加载 shell 后，dtm 自动补全应该就可以正常使用了！
-
-#### MacOS
-
-```{admonition} Note
-:class: note
-主要参考了 [Install and Set Up kubectl on macOS](https://kubernetes.io/docs/tasks/tools/install-kubectl-macos/#enable-shell-autocompletion)
-```
-
-自动补全脚本依赖于 `bash-completion`, 需要提前安装：
-
-```bash
-brew install bash-completion@2
-```
-
-正如以上命令的输出所述，请在 `~/.bash_profile` 文件中添加以下内容：
-
-```bash
-brew_etc="$(brew --prefix)/etc"
-echo "[[ -r \"${brew_etc}/profile.d/bash_completion.sh\" ]] && . \"${brew_etc}/profile.d/bash_completion.sh\"" >>~/.bash_profile
-source ~/.bash_profile
-```
-
-重新加载 shell，用 `type _init_completion` 验证 bash-completion v2 是否正确安装。
-
-接着，用 `dtm completion bash` 命令为 Bash 生成自动补全脚本。 执行以下命令，以将相应内容添加到 `~/.bashrc` 中：
-
-```bash
-echo 'source <(dtm completion bash)' >>~/.bash_profile
-source ~/.bash_profile
-```
-
-在重新加载 shell 后，dtm 自动补全应该就可以正常使用了！
-
-### Zsh 自动补全
-
-你可以用 `dtm completion zsh` 命令为 Zsh 生成自动补全脚本。 执行以下命令，以将相应内容添加到 `~/.zshrc` 中：
-
-```zsh
-echo 'source <(dtm completion zsh)' >>~/.zshrc
-source ~/.zshrc
-```
-
-在重新加载 shell 后，dtm 自动补全应该就可以正常使用了！
-
-### Fish 自动补全
-
-你可以用 `dtm completion fish` 命令为 Fish 生成自动补全脚本。然后将以下行添加到 `~/.config/fish/config.fish` 文件中：
-
-```fish
-dtm completion fish | source
-```
-
-在重新加载 shell 后，dtm 自动补全应该就可以正常使用了！
-
-### PowerShell 自动补全
-
-你可以用 `dtm completion powershell` 命令为 PowerShell 生成自动补全脚本。然后将以下行添加到 `$PROFILE` 文件中：
-
-```powershell
-dtm completion powershell | Out-String | Invoke-Expression
-```
-
-这个命令会在每次 PowerShell 启动时重新生成自动补全脚本。你也可以直接将生成的脚本添加到 `$PROFILE` 文件中。
-
-为了将生成的脚本添加到 `$PROFILE` 文件中，请在 PowerShell 提示符中运行以下行：
-
-```powershell
-dtm completion powershell >> $PROFILE
-```
-
-在重新加载 shell 后，dtm 自动补全应该就可以正常使用了！
diff --git a/docs/commands/delete.md b/docs/commands/delete.md
deleted file mode 100644
index b7b950da2..000000000
--- a/docs/commands/delete.md
+++ /dev/null
@@ -1,27 +0,0 @@
-# dtm delete
-
-## 1 Normal (Non-Force) Delete
-
-When _deleting_ using `dtm delete`, here's what happens:
-
-- Read the _Config_
-- For each _Tool_ defined in the _Config_, if there is a corresponding _State_, the `Delete` interface will be called.
-
-_Note: the `Delete` change will be executed only if the _State_ exists._
-
-## 2 Force Delete
-
-When _deleting_ using `dtm delete --force`, here's what happens:
-
-- Read the _Config_
-- The `Delete` interface will be called for each _Tool_ defined in the _Config_.
-
-_Note: the difference between "force delete" and "normal delete" is that in force mode, no matter the _State_ exists or not, `dtm` will try to trigger the `Delete` interface. The purpose is for corner cases where the state gets corrupted or even lost during testing (I hope this only happens in the development environment), there is still a way to clean up the _Tools_._
-
-## 3 Flags
-| Short | Long | Default | Description |
-|-------|---------------|--------------------------|---------------------------------------|
-| | --force | `false` | Force delete by config. |
-| -f | --config-file | `"config.yaml"` | The path to the config file. |
-| -d | --plugin-dir | `"~/.devstream/plugins"` | The path to plugins. |
-| -y | --yes | `false` | Delete directly without confirmation. |
diff --git a/docs/commands/delete.zh.md b/docs/commands/delete.zh.md
deleted file mode 100644
index 2195df529..000000000
--- a/docs/commands/delete.zh.md
+++ /dev/null
@@ -1,28 +0,0 @@
-# dtm delete
-
-## 1 普通（非强制）删除
-
-使用 `dtm delete` 执行 _删除_ 时，会发生：
-
-- 读取 _Config_
-- 对于 _Config_ 中定义的每一个 _Tool_，如果有对应的 _State_，就会调用 `Delete` 接口。
-
-_注意：`Delete` 操作只会在 _State_ 存在时执行。_
-
-## 2 强制删除
-
-使用 `dtm delete --force` 执行 _强制删除_ 时，会发生：
-
-- 读取 _Config_
-- 对于 _Config_ 中定义的每一个 _Tool_，调用 `Delete` 接口。
-
-_说明："普通删除"和"强制删除"的区别在于，无论 _State_ 是否存在，`dtm` 都会尝试调用 `Delete` 接口。此举目的在于，当 _State_ 损坏甚至丢失时（我们希望这只发生在开发环境），仍能有办法清除 _Tools_。
-
-## 3 命令行参数
-
-| 短 | 长 | 默认值 | 描述 |
-|-----|---------------|--------------------------|------------|
-| | --force | `false` | 强制删除 |
-| -f | --config-file | `"config.yaml"` | 配置文件路径 |
-| -d | --plugin-dir | `"~/.devstream/plugins"` | 插件目录 |
-| -y | --yes | `false` | 取消二次确认 |
diff --git a/docs/commands/destroy.md b/docs/commands/destroy.md
deleted file mode 100644
index 7f452d5cd..000000000
--- a/docs/commands/destroy.md
+++ /dev/null
@@ -1,14 +0,0 @@
-# dtm destroy
-
-`dtm destroy` acts like `dtm apply -f an_empty_config.yaml`.
-
-The purpose of `destroy` is that in case you accidentally deleted your config file during testing, there would still be a way to destroy everything that is defined in the _State_ so that you can have a clean state.
-
-## 1 Flags
-
-| Short | Long | Default | Description |
-|-------|---------------|---------|----------------------------------------|
-| | --force | `false` | Force destroy by config. |
-| -d | --plugin-dir | `"~/.devstream/plugins"` | The path to plugins. |
-| -f | --config-file | `"config.yaml"` | The path to the config file. |
-| -y | --yes | `false` | Destroy directly without confirmation. |
diff --git a/docs/commands/destroy.zh.md b/docs/commands/destroy.zh.md
deleted file mode 100644
index cee63dcce..000000000
--- a/docs/commands/destroy.zh.md
+++ /dev/null
@@ -1,14 +0,0 @@
-# dtm destroy
-
-`dtm destroy` 的效果类似于 `dtm apply -f an_empty_config.yaml`.
-
-`destroy` 命令的目的在于，一旦你在测试的时候不小心删除了配置文件，仍能通过此方式删除 _State_ 中定义的所有内容，以拥有干净的环境。
-
-## 1 命令行参数
-
-| 短 | 长 | 默认值 | 描述 |
-|-----|---------------|--------------------------|------------|
-| | --force | `false` | 强制删除 |
-| -d | --plugin-dir | `"~/.devstream/plugins"` | 插件目录 |
-| -f | --config-file | `"config.yaml"` | 配置文件路径 |
-| -y | --yes | `false` | 取消二次确认 |
diff --git a/docs/commands/develop.md b/docs/commands/develop.md
deleted file mode 100644
index 9f92c78db..000000000
--- a/docs/commands/develop.md
+++ /dev/null
@@ -1,28 +0,0 @@
-# dtm develop
-
-`dtm develop` is used to develop a new plugin for anything.
-
-## 1 Brief
-
-`dtm develop create-plugin` generates plugin scaffolding based on dtm [pre-built templates](https://github.com/devstream-io/devstream/tree/main/internal/pkg/develop/plugin/template).
-
-`dtm develop validate-plugin` is used for verifying whether all the necessary files required for the plugin exist
-
-## 2 Full Process Guide
-
-A detailed guide to the plugin development process can be found in [creating a plugin](../development/dev/creating-a-plugin.md).
-
-## 3 Flags
-
-`dtm develop create-plugin`:
-
-| Short | Long | Default | Description |
-|-------|--------|---------|------------------------------------------|
-| -n | --name | `""` | specify name of the plugin to be created |
-
-`dtm develop validate-plugin`:
-
-| Short | Long | Default | Description |
-|-------|--------|---------|--------------------------------------------|
-| -n | --name | `""` | specify name of the plugin to be validated |
-| -a | --all | `false` | validate all plugins |
diff --git a/docs/commands/develop.zh.md b/docs/commands/develop.zh.md
deleted file mode 100644
index 3df669b37..000000000
--- a/docs/commands/develop.zh.md
+++ /dev/null
@@ -1,27 +0,0 @@
-# dtm develop
-
-`dtm develop` 用于开发一个新的插件，做任何你想做的事情。
-
-## 1 简介
-
-- `dtm develop create-plugin` 根据[dtm 插件模板](https://github.com/devstream-io/devstream/tree/main/internal/pkg/develop/plugin/template)生成插件脚手架。
-- `dtm develop validate-plugin` 用于验证插件所需的必要文件是否都存在。
-
-## 2 完整插件开发指南
-
-插件开发的详细指南可以在[创建一个插件](../development/dev/creating-a-plugin.zh.md)找到。
-
-## 3 命令行参数
-
-`dtm develop create-plugin`:
-
-| 短 | 长 | 默认值 | 描述 |
-|-----|--------|-------|-----------------|
-| -n | --name | `""` | 要创建的插件的名称 |
-
-`dtm develop validate-plugin`:
-
-| 短 | 长 | 默认值 | 描述 |
-|-----|--------|---------|-----------------|
-| -n | --name | `""` | 要验证的插件的名称 |
-| -a | --all | `false` | 验证所有插件 |
diff --git a/docs/commands/fig/cmd-help.gif b/docs/commands/fig/cmd-help.gif
deleted file mode 100644
index 5946ff06b..000000000
Binary files a/docs/commands/fig/cmd-help.gif and /dev/null differ
diff --git a/docs/commands/fig/cmd-make.gif b/docs/commands/fig/cmd-make.gif
deleted file mode 100644
index 3c3285323..000000000
Binary files a/docs/commands/fig/cmd-make.gif and /dev/null differ
diff --git a/docs/commands/fig/cmd-show-plugins.gif b/docs/commands/fig/cmd-show-plugins.gif
deleted file mode 100644
index 851cb6d39..000000000
Binary files a/docs/commands/fig/cmd-show-plugins.gif and /dev/null differ
diff --git a/docs/commands/fig/fig-intro.gif b/docs/commands/fig/fig-intro.gif
deleted file mode 100644
index 7dd68d1ae..000000000
Binary files a/docs/commands/fig/fig-intro.gif and /dev/null differ
diff --git a/docs/commands/fig/fig-terminal.png b/docs/commands/fig/fig-terminal.png
deleted file mode 100644
index 08bf1e9de..000000000
Binary files a/docs/commands/fig/fig-terminal.png and /dev/null differ
diff --git a/docs/commands/init.md b/docs/commands/init.md
deleted file mode 100644
index f4bc99070..000000000
--- a/docs/commands/init.md
+++ /dev/null
@@ -1,49 +0,0 @@
-# dtm init
-
-`dtm` releases plugins to an AWS S3 bucket.
-
-When running `dtm init`, it will download plugins from the AWS S3 bucket(through Cloudflare CDN.)
-
-There are two ways to download plugins:
-
-1. from config file: download plugins according to `tools` and `apps` in the config
-2. from command line: download plugins according to the command line arguments
-
-## Downloading Plugins from Config File
-
-In this way, `dtm init` will download the required plugins according to `tools` and `apps` in the config.
-
-**command:** `dtm init -f
-
-
-
-## What Does DevStream Do
-
-- Kickoff DevOps in 5 minutes: tired of investigating and integrating all the DevOps tools? Get your open-source, customized DevOps toolchain up and running with one command.
-- Build your DevOps toolchain like Lego: boost team productivity by plugging in, replacing, or upgrading the tool of your choice with minimal operational overhead. Unleash the full potential of your toolchain with best practices.
-- Embrace new opportunities: say goodbye to vendor lock-in. Never let your toolchain become your bottleneck. Feel the pulse of new DevOps tools, methodologies, and practices.
-
-## Why Use DevStream
-
-- Too much effort maintaining every piece of DevOps tool?
-- Too challenging (if not impossible) to track who changed what?
-- Too much hassle replacing some of your DevOps tools that you would choose "if it ain't broke, don't fix it"?
-- Small team, many tools, and way too few DevOps engineers to fully implement your pipelines?
-
-Worry no more. DevStream got you covered.
-
-## Under the Hood
-
-- DevOps toolchain as code: centrally manage your toolchain with version-controlled code, and keep track of everything.
-- Core-Plugin architecture: no reinventing the wheel. Reuse or even create a plugin, and connect any tools you like with DevStream.
-- Best practice templates: choose our recommended best-practice toolchain template that suits your needs. Implement built-in best practices and share yours with the world.
-
-## Useful Links
-
-- [GitHub](https://github.com/devstream-io/devstream)
-- [Website](https://www.devstream.io)
-- [Blog](https://blog.devstream.io)
-- [Community](https://www.devstream.io/community/)
diff --git a/docs/index.zh.md b/docs/index.zh.md
deleted file mode 100644
index 39cada768..000000000
--- a/docs/index.zh.md
+++ /dev/null
@@ -1,45 +0,0 @@
-# DevStream：你的 DevOps 工具链管理器
-
-## 什么是 DevStream？
-
-DevStream 是一个开源的 DevOps 工具链管理器，因开发者而生，由开发者开发，为开发者服务。
-
-探索最适合你的 DevOps 实践，DevStream 将负责剩余的工作。
-
-TL;DR：只需观看以下演示:
-
-
-
-
-
-!!! hint "提示"
-
- 跳转到B站观看清晰度更高。
-
-## DevStream 做了什么？
-
-- 5分钟内启动 DevOps：你是否厌倦了调研并整合所有的 DevOps 组件？现在只需一个命令就能启动并运行你的开源、定制的 DevOps 工具链。
-- 像乐高积木一样构建你的 DevOps 工具链：通过插拔、替换或升级你选择的组件，以最低的开销提高团队生产力；利用最佳实践释放你的工具链的全部潜力。
-- 拥抱新的机遇：告别服务商的限制；不要让你的工具链成为你的瓶颈；感受新 DevOps 工具、方法论和实践的脉搏跳动。
-
-## 为什么使用 DevStream？
-
-- 维护 DevOps 组件的工作量太大？
-- 追踪项目状态改变过于复杂？
-- 更换 DevOps 组件太麻烦了，你会选择 "如果没坏就不要修"？
-- 小团队，大组件，没有 DevOps 工程师来完美实现你的项目流水线？
-
-无需担心，DevStream 将解决这一切。
-
-## 深度揭秘 DevStream
-
-- DevOps 工具链即代码：使用版本控制下的代码集中管理你的工具链，并追踪一切。
-- Core-Plugin 架构：无需重新造轮子，而是复用甚至创建一个插件，用 DevStream 连接你喜欢的任何组件。
-- 最佳实践模板：选择推荐适合你的最佳实践工具链模板。实现自带的最佳实践，并与世界分享你的最佳实践。
-
-## 链接
-
-- [GitHub](https://github.com/devstream-io/devstream)
-- [官网](https://www.devstream.io)
-- [博客](https://blog.devstream.io)
-- [社区](https://www.devstream.io/community/)
diff --git a/docs/install.md b/docs/install.md
deleted file mode 100644
index e79e29fbd..000000000
--- a/docs/install.md
+++ /dev/null
@@ -1,62 +0,0 @@
-# Installation
-
-!!! note
- Currently supported operating systems and chip architectures:
-
- 1. Darwin/arm64
- 2. Darwin/amd64
- 3. Linux/amd64
-
-## 1 Install dtm binary with script
-
-In your working directory, run:
-
-```shell
-sh -c "$(curl -fsSL https://download.devstream.io/download.sh)"
-```
-
-This will download the corresponding `dtm` binary to your working directory according to your OS and chip architecture, and grant the binary execution permission.
-
-!!! note "Optional"
-
- Move `dtm` to a place which is in your PATH. For example: `mv dtm /usr/local/bin/`.
-
-## 2 Download manually from the GitHub Release page
-
-You could find the latest version of `dtm` on the [Release](https://github.com/devstream-io/devstream/releases/) page and click Download.
-
-If your browser isn't working properly, "curl" is also a good option:
-
-```shell
-# Version v0.10.3, OS type linux and CPU arch amd64 need to be modified as needed
-$ curl -o dtm https://download.devstream.io/v0.10.3/dtm-linux-amd64
-```
-
-Note that there are multiple versions of `dtm` available, so you will need to choose the correct version for your operating system and chip architecture. Once downloaded locally, you can choose to rename it, move it to the directory containing `$PATH` and give it executable permissions, for example, on Linux you can do this by running the following command.
-
-```shell
-mv dtm-linux-amd64 /usr/local/bin/dtm
-chmod +x dtm
-```
-
-Then you can verify that the permissions and version of dtm are correct with the following command.
-
-```shell
-$ dtm version
-0.10.3
-```
-
-## 3 Install dtm with [asdf](https://asdf-vm.com/)
-
-```shell
-# Plugin
-asdf plugin add dtm
-# Show all installable versions
-asdf list-all dtm
-# Install specific version
-asdf install dtm latest
-# Set a version globally (on your ~/.tool-versions file)
-asdf global dtm latest
-# Now dtm commands are available
-dtm help
-```
diff --git a/docs/install.zh.md b/docs/install.zh.md
deleted file mode 100644
index 40596eb3d..000000000
--- a/docs/install.zh.md
+++ /dev/null
@@ -1,62 +0,0 @@
-# 安装
-
-!!! note "提示"
- 当前 dtm 发行版支持如下操作系统与 CPU 架构组合：
-
- 1. Darwin/arm64
- 2. Darwin/amd64
- 3. Linux/amd64
-
-## 1 用脚本安装
-
-进入你的工作目录，运行：
-
-```shell
-sh -c "$(curl -fsSL https://download.devstream.io/download.sh)"
-```
-
-这个命令会根据你的操作系统和芯片架构下载对应的 `dtm` 二进制文件到你的工作目录中，并赋予二进制文件执行权限。
-
-!!! note "可选"
-
- 将 dtm 移动到包含于 PATH 的目录下，比如 `mv dtm /usr/local/bin/`。
-
-## 2 从 GitHub Release 页面手动下载安装
-
-在 [Release](https://github.com/devstream-io/devstream/releases/) 页面找到当前最新版本 `dtm`，然后点击下载。
-
-如果你不方便使用浏览器下载，也可以选择使用 curl：
-
-```shell
-# 版本号 v0.10.3，系统类型 linux 和 CPU 架构 amd64 根据需要灵活修改
-$ curl -o dtm https://download.devstream.io/v0.10.3/dtm-linux-amd64
-```
-
-需要注意的是当前 `dtm` 提供了多个版本，你需要根据操作系统和芯片架构选择自己需要的正确版本。下载到本地后，你可以选择将其重命名，移入包含在"$PATH"的目录里并赋予其可执行权限，比如在 Linux 上你可以执行如下命令完成这些操作：
-
-```shell
-mv dtm-linux-amd64 /usr/local/bin/dtm
-chmod +x dtm
-```
-
-接着你可以通过如下命令验证 dtm 的权限以及版本等是否正确：
-
-```shell
-$ dtm version
-0.10.3
-```
-
-## 3 用 [asdf](https://asdf-vm.com/) 安装
-
-```shell
-# 安装 dtm 插件
-asdf plugin add dtm
-# 列出所有可用版本
-asdf list-all dtm
-# 安装特定版本
-asdf install dtm latest
-# 设置全局版本 (在 ~/.tool-versions 文件中)
-asdf global dtm latest
-# 现在你就能使用 dtm 了
-dtm help
-```
diff --git a/docs/plugins/argocdapp.md b/docs/plugins/argocdapp.md
deleted file mode 100644
index 8561d3041..000000000
--- a/docs/plugins/argocdapp.md
+++ /dev/null
@@ -1,102 +0,0 @@
-# argocdapp Plugin
-
-This plugin creates an [Argo CD Application](https://argo-cd.readthedocs.io/en/stable/core_concepts/) custom resource.
-
-**Notes:**
-
-- Argo CD itself must have been already installed before the usage of this plugin.
- To install Argo CD, use the [helm-installer plugin](./helm-installer/argocd.md).
- Or you can use both plugins(argocd+argocdapp) at the same time.
- See [GitOps Toolchain](../use-cases/gitops/2-gitops-tools.md) for more info.
-- Currently, only the Helm chart is supported when creating the Argo CD application.
-
-## Usage
-
-The following content is an example of the "tool file".
-
-For more information on the main config, the tool file and the var file of DevStream, see [Core Concepts Overview](../core-concepts/overview.md) and [DevStream Configuration](../core-concepts/config.md).
-
-```yaml
---8<-- "argocdapp.yaml"
-```
-
-### Automatically Create Helm Configuration
-
-This plugin can push helm configuration automatically when your `source.path` helm config does not exist so that you can use this plugin with helm configured already. For example:
-
-```yaml
----
-tools:
-- name: go-webapp-argocd-deploy
- plugin: argocdapp
- dependsOn: ["repo-scaffolding.golang-github"]
- options:
- app:
- name: hello
- namespace: argocd
- destination:
- server: https://kubernetes.default.svc
- namespace: default
- source:
- valuefile: values.yaml
- path: charts/go-hello-http
- repoURL: https://github.com/devstream-io/testrepo.git
- imageRepo:
- url: http://test.barbor.com/library
- user: test_owner
- tag: "1.0.0"
-```
-
-This config will push the default [helm config](https://github.com/devstream-io/dtm-pipeline-templates/tree/main/argocdapp/helm)](https://github.com/devstream-io/dtm-pipeline-templates/tree/main/argocdapp/helm) to repo [testrepo](https://github.com/devstream-io/testrepo.git), and the generated config will use the image `http://test.barbor.com/library/test_owner/hello:1.0.0` as the initial image for Helm.
-
-## Use Together with the `repo-scaffolding` Plugin
-
-This plugin can be used together with the `repo-scaffolding` plugin (see document [here](./repo-scaffolding.md).)
-
-For example, you can first use `repo-scaffolding` to bootstrap a Golang repo, then use this plugin to set up basic GitHub Actions CI workflows. In this scenario:
-
-- This plugin can specify `repo-scaffolding` as a dependency, so that the dependency is first satisfied before executing this plugin.
-- This plugin can refer to `repo-scaffolding`'s output to reduce copy/paste human error.
-
-See the example below:
-
-```yaml
----
-tools:
-- name: repo-scaffolding
- instanceID: golang-github
- options:
- destinationRepo:
- owner: [[ githubUsername ]]
- org: ""
- name: [[ repoName ]]
- branch: [[ defaultBranch ]]
- scmType: github
- vars:
- imageRepo: "[[ dockerhubUsername ]]/[[ repoName ]]"
- sourceRepo:
- org: devstream-io
- name: dtm-scaffolding-golang
- scmType: github
-- name: go-webapp-argocd-deploy
- plugin: argocdapp
- dependsOn: ["repo-scaffolding.golang-github"]
- options:
- app:
- name: hello
- namespace: argocd
- destination:
- server: https://kubernetes.default.svc
- namespace: default
- source:
- valuefile: values.yaml
- path: charts/go-hello-http
- repoURL: ${{repo-scaffolding.golang-github.outputs.repoURL}}
-```
-
-In the example above:
-
-- We put `repo-scaffolding.golang-github` as dependency by using the `dependsOn` keyword.
-- We used `repo-scaffolding.golang-github`'s output as input for the `github-actions` plugin.
-
-Pay attention to the `${{ xxx }}` part in the example. `${{ TOOL_NAME.PLUGIN.outputs.var}}` is the syntax for using an output.
diff --git a/docs/plugins/argocdapp.zh.md b/docs/plugins/argocdapp.zh.md
deleted file mode 100644
index c1f2a680e..000000000
--- a/docs/plugins/argocdapp.zh.md
+++ /dev/null
@@ -1,45 +0,0 @@
-# argocdapp 插件
-
-该插件会创建一个在 Kubernetes 上 [Argo CD Application](https://argo-cd.readthedocs.io/en/stable/core_concepts/) 的自定义资源。
-
-**注意:**
-
-- 在使用该插件前需要先安装 Argocd CD。你可以使用 [helm-installer 插件](./helm-installer/argocd.md) 来安装它。
-- 目前该插件只支持 Helm chart 的配置方式。
-
-## 用例
-
-以下内容是该插件的示例配置文件。
-
-```yaml
---8<-- "argocdapp.yaml"
-```
-
-### 自动创建 Helm 配置
-
-如果你不想要自己创建 Helm 配置，该插件支持把 Devstream 提供的默认 Helm 配置上传到 `source.path` 的配置路径上，这样你就可以直接使用该插件。配置示例如下：
-
-```yaml
----
-tools:
-- name: go-webapp-argocd-deploy
- plugin: argocdapp
- dependsOn: ["repo-scaffolding.golang-github"]
- options:
- app:
- name: hello
- namespace: argocd
- destination:
- server: https://kubernetes.default.svc
- namespace: default
- source:
- valuefile: values.yaml
- path: charts/go-hello-http
- repoURL: https://github.com/devstream-io/testrepo.git
- imageRepo:
- url: http://test.barbor.com/library
- user: test_owner
- tag: "1.0.0"
-```
-
-这个示例配置将会把 [Helm 配置](https://github.com/devstream-io/dtm-pipeline-templates/tree/main/argocdapp/helm) 上传到 [testrepo](https://github.com/devstream-io/testrepo.git) 仓库中，生成的 Helm 配置会使用 `http://test.barbor.com/library/test_owner/hello:1.0.0` 作为 Helm 应用的启动镜像。
\ No newline at end of file
diff --git a/docs/plugins/ci-generic.md b/docs/plugins/ci-generic.md
deleted file mode 100644
index 0668ca315..000000000
--- a/docs/plugins/ci-generic.md
+++ /dev/null
@@ -1,63 +0,0 @@
-# ci-generic Plugin
-
-This plugin installs `CI` script in `GitLib`/`GitHub` repo from a local or remote url.
-
-## Usage
-
-The following content is an example of the "tool file".
-
-For more information on the main config, the tool file and the var file of DevStream, see [Core Concepts Overview](../core-concepts/overview.md) and [DevStream Configuration](../core-concepts/config.md).
-
-``` yaml
---8<-- "ci-generic.yaml"
-```
-
-**Notes:**
-
-- `projectRepo` config option represents codebase location; for more info, you can refer to [SCM Config](./scm-option.md).
-- `ci.localPath` and `ci.remoteURL` can't be empty at the same time.
-- if your `projectRepo.scmType` is `gitlab`, the `ci.type` is not allowed to be `github-actions`.
-- if your `projectRepo.scmType` is `github`, the `ci.type` is not allowed to be `gitlab-ci`.
-
-## Example
-
-### Local WorkFlows With Github
-
-```yaml
-tools:
-- name: ci-generic
- instanceID: test-github
- options:
- ci:
- localPath: workflows
- type: github
- projectRepo:
- owner: devstream
- org: ""
- name: test-repo
- branch: main
- scmType: github
-```
-
-This config will put local workflows directory to GitHub repo's .github/workflows directory.
-
-### Remote Jenkinsfile With Gitlab
-
-```yaml
-tools:
-- name: ci-generic
- instanceID: test-gitlab
- options:
- ci:
- remoteURL : https://raw.githubusercontent.com/DeekshithSN/Jenkinsfile/inputTest/Jenkinsfile
- type: jenkins
- projectRepo:
- owner: root
- org: ""
- name: test-repo
- branch: main
- scmType: gitlab
- baseURL: http://127.0.0.1:30000
-```
-
-This config will put files from [remote](https://raw.githubusercontent.com/DeekshithSN/Jenkinsfile/inputTest/Jenkinsfile)](https://raw.githubusercontent.com/DeekshithSN/Jenkinsfile/inputTest/Jenkinsfile) to GitLab repo.
diff --git a/docs/plugins/ci-generic.zh.md b/docs/plugins/ci-generic.zh.md
deleted file mode 100644
index 08a75fdc9..000000000
--- a/docs/plugins/ci-generic.zh.md
+++ /dev/null
@@ -1,111 +0,0 @@
-# ci-generic 插件
-
-这个插件可以基于本地或者远程的文件在 GitLab/GitHub 安装 CI 配置
-
-## 用例
-
-下面的配置文件展示的是"tool file"的内容。
-
-关于更多关于DevStream的主配置、tool file、var file的信息，请阅读[核心概念概览](../core-concepts/overview.zh.md)和[DevStream配置](../core-concepts/config.zh.md).
-
-``` yaml
---8<-- "ci-generic.yaml"
-```
-
-**注意事项：**
-
-- `projectRepo` 配置字段用于表示代码仓库的配置信息，具体配置可查看[SCM配置项](./scm-option.zh.md)
-- `ci.configContents` 和 `ci.configLocation` 不能同时为空。
-- 如果你配置了 `projectRepo.scmType` 为 `github`，那 `ci.type` 就不能是 `gitlab-ci`。
-- 如果你配置了 `projectRepo.scmType` 为 `gitlab`，那 `ci.type` 就不能是 `github-actions`。
-
-## 示例
-
-### 使用本地的 Workflows 目录
-
-```yaml
-tools:
-- name: ci-generic
- instanceID: test-github
- options:
- ci:
- configLocation: workflows
- type: github
- projectRepo:
- owner: devstream
- org: ""
- name: test-repo
- branch: main
- scmType: github
-```
-
-这个配置将会把本地当前运行环境下的 workflows 目录放置于 GitHub 的 `.github/workflows` 目录。
-
-### 使用 HTTP 获取远程的CI文件
-
-```yaml
-tools:
-- name: ci-generic
- instanceID: test-gitlab
- options:
- ci:
- configLocation : https://raw.githubusercontent.com/DeekshithSN/Jenkinsfile/inputTest/Jenkinsfile
- type: jenkins
- projectRepo:
- owner: root
- org: ""
- name: test-repo
- branch: main
- scmType: gitlab
- baseURL: http://127.0.0.1:30000
-```
-
-这个配置将会把[URL](https://raw.githubusercontent.com/DeekshithSN/Jenkinsfile/inputTest/Jenkinsfile) 中的 Jenkinsfile 文件置于 GitLab 的仓库。
-
-### 使用Github仓库中的CI文件
-```yaml
-tools:
-- name: ci-generic
- instanceID: test-gitlab
- options:
- ci:
- configLocation : git@github.com:devstream-io/devstream.git//staging/dtm-jenkins-pipeline-example/general
- type: jenkins
- projectRepo:
- owner: root
- org: ""
- name: test-repo
- branch: main
- scmType: gitlab
- baseURL: http://127.0.0.1:30000
-```
-
-这个配置将会搜索[devstream 仓库](https://github.com/devstream-io/devstream)下的staging/dtm-jenkins-pipeline-example/general 目录，获取到目录下的 Jenkinsfile，置于 gitlab 仓库内。
-
-### 在Devstream中直接配置CI文件
-
-```yaml
-tools:
-- name: ci-generic
- instanceID: test-gitlab
- options:
- ci:
- configContents:
- pr.yaml: |
-name: GitHub Actions Demo
-run-name: ${{ github.actor }} is testing out GitHub Actions 🚀
-on: [push]
-jobs:
- Explore-GitHub-Actions:
- runs-on: ubuntu-latest
- steps:
- - run: echo "🎉 The job was automatically triggered by a ${{ github.event_name }} event."
- projectRepo:
- owner: test-user
- org: ""
- name: test-repo
- branch: main
- scmType: github
-```
-
-这个配置将会在用户的Github仓库`test-user/test-repo`下创建`.github/workflows/pr.yaml`文件。
diff --git a/docs/plugins/devlake-config.md b/docs/plugins/devlake-config.md
deleted file mode 100644
index 8365b2a98..000000000
--- a/docs/plugins/devlake-config.md
+++ /dev/null
@@ -1,9 +0,0 @@
-# devlake-config plugin
-
-TODO(dtm): Add your document here.
-
-## Usage
-
-``` yaml
---8<-- "devlake-config.yaml"
-```
diff --git a/docs/plugins/devlake-config.zh.md b/docs/plugins/devlake-config.zh.md
deleted file mode 100644
index c6496fb55..000000000
--- a/docs/plugins/devlake-config.zh.md
+++ /dev/null
@@ -1,9 +0,0 @@
-# devlake-config 插件
-
-TODO(dtm): 在这里添加文档.
-
-## 用例
-
-``` yaml
---8<-- "devlake-config.yaml"
-```
diff --git a/docs/plugins/github-actions.md b/docs/plugins/github-actions.md
deleted file mode 100644
index f1128ed35..000000000
--- a/docs/plugins/github-actions.md
+++ /dev/null
@@ -1,14 +0,0 @@
-# github-actions plugin
-
-This plugin is used to create `Github Workflows` in your project.
-
-## Usage
-
-``` yaml
---8<-- "github-actions.yaml"
-```
-
-**Notes:**
-
-- `scm` config option represents codebase location; for more info, you can refer to [SCM Config](./scm-option.md).
-- The `pipeline` config option controls `CI` stages; you can refer to [Pipeline Config](./pipeline.md) for more info.
diff --git a/docs/plugins/github-actions.zh.md b/docs/plugins/github-actions.zh.md
deleted file mode 100644
index e02a0976c..000000000
--- a/docs/plugins/github-actions.zh.md
+++ /dev/null
@@ -1,16 +0,0 @@
-# github-actions 插件
-
-_该插件用于在项目中创建 Github Action Workflows。_
-
-## 用例
-
-下面的内容是一个示例配置文件用于创建 Github Workflows：
-
-``` yaml
---8<-- "github-actions.yaml"
-```
-
-**注意:**
-
-- `scm` 配置字段用于表示代码仓库的配置信息，具体配置可查看[SCM配置项](./scm-option.zh.md)。
-- `pipeline` 选项项用于控制 `CI` 流程中的各个阶段，具体配置可查看文档[pipline配置项](pipeline.zh.md)。
\ No newline at end of file
diff --git a/docs/plugins/gitlab-ce-docker.md b/docs/plugins/gitlab-ce-docker.md
deleted file mode 100644
index cca158893..000000000
--- a/docs/plugins/gitlab-ce-docker.md
+++ /dev/null
@@ -1,87 +0,0 @@
-# gitlab-ce-docker Plugin
-
-This plugin installs [GitLab](https://about.gitlab.com/) CE(Community Edition) on Docker.
-
-_NOTICE: currently, this plugin support Linux only._
-
-## Background
-
-GitLab officially provides an image [gitlab-ce](https://registry.hub.docker.com/r/gitlab/gitlab-ce). We can use this image to start a container:
-
-```shell
-docker run --detach \
- --hostname gitlab.example.com \
- --publish 443:443 --publish 80:80 --publish 22:22 \
- --name gitlab \
- --restart always \
- --volume $GITLAB_HOME/config:/etc/gitlab \
- --volume $GITLAB_HOME/logs:/var/log/gitlab \
- --volume $GITLAB_HOME/data:/var/opt/gitlab \
- --shm-size 256m \
- gitlab/gitlab-ce:rc
-```
-
-The variable `$GITLAB_HOME` here pointing to the directory where the configuration, logs, and data files will reside.
-
-We can set this variable by the `export` command:
-
-```shell
-export GITLAB_HOME=/srv/gitlab
-```
-
-The GitLab container uses host mounted volumes to store persistent data:
-
-| Local location |Container location | Usage |
-| --------------------- | ----------------- | ------------------------------------------ |
-| `$GITLAB_HOME/data` | `/var/opt/gitlab` | For storing application data |
-| `$GITLAB_HOME/logs` | `/var/log/gitlab` | For storing logs |
-| `$GITLAB_HOME/config` | `/etc/gitlab` | For storing the GitLab configuration files |
-
-So, we can customize the following configurations:
-
-1. hostname
-2. host port
-3. persistent data path
-4. docker image tag
-
-## Configuration
-
-Note:
-1. the user you are using must be `root` or in the `docker` group;
-2. `https` isn't supported for now.
-
-The following content is an example of the "tool file".
-
-For more information on the main config, the tool file and the var file of DevStream, see [Core Concepts Overview](../core-concepts/overview.md) and [DevStream Configuration](../core-concepts/config.md).
-
-```yaml
---8<-- "gitlab-ce-docker.yaml"
-```
-
-## Some Commands That May Help
-
-- clone code
-
-```shell
-export hostname=YOUR_HOSTNAME
-export username=YOUR_USERNAME
-export project=YOUR_PROJECT_NAME
-```
-
-1. ssh
-
-```shell
-# port is 22
-git clone git@${hostname}/${username}/${project}.git
-# port is not 22, 2022 as a sample
-git clone ssh://git@${hostname}:2022/${username}/${project}.git
-```
-
-2. http
-
-```shell
-# port is 80
-git clone http://${hostname}/${username}/${project}.git
-# port is not 80, 8080 as a sample
-git clone http://${hostname}:8080/${username}/${project}.git
-```
diff --git a/docs/plugins/gitlab-ce-docker.zh.md b/docs/plugins/gitlab-ce-docker.zh.md
deleted file mode 100644
index ddd286345..000000000
--- a/docs/plugins/gitlab-ce-docker.zh.md
+++ /dev/null
@@ -1,85 +0,0 @@
-# gitlab-ce-docker 插件
-
-这个插件用于以 Docker 的方式安装 [GitLab](https://about.gitlab.com/) CE（社区版）。
-
-_注意：目前本插件仅支持 Linux。_
-
-## 背景知识
-
-GitLab 官方提供了 [gitlab-ce](https://registry.hub.docker.com/r/gitlab/gitlab-ce) 镜像，通过这个镜像我们可以实现类似这样的命令来启动一个 GitLab 容器：
-
-```shell
-docker run --detach \
- --hostname gitlab.example.com \
- --publish 443:443 --publish 80:80 --publish 22:22 \
- --name gitlab \
- --restart always \
- --volume $GITLAB_HOME/config:/etc/gitlab \
- --volume $GITLAB_HOME/logs:/var/log/gitlab \
- --volume $GITLAB_HOME/data:/var/opt/gitlab \
- --shm-size 256m \
- gitlab/gitlab-ce:rc
-```
-
-其中 $GITLAB_HOME 表示的是本地存储卷路径，比如我们可以通过 export 命令来设置这个变量：
-
-```shell
-export GITLAB_HOME=/srv/gitlab
-```
-
-在上述命令中，我们可以看到这个容器使用了3个存储卷，含义分别如下：
-
-| 本地路径 | 容器内路径 | 用途 |
-| --------------------- | ----------------- | ----------------- |
-| `$GITLAB_HOME/data` | `/var/opt/gitlab` | 保存应用数据 |
-| `$GITLAB_HOME/logs` | `/var/log/gitlab` | 保存日志 |
-| `$GITLAB_HOME/config` | `/etc/gitlab` | 保存 GitLab 配置文件 |
-
-在此基础上，我们可以自定义如下一些配置：
-
-1. hostname
-2. 本机端口
-3. 存储卷路径
-4. 镜像版本
-
-## 配置
-
-注意:
-1. 你使用的用户必须是 `root` 或者在 `docker` 用户组里；
-2. 目前暂不支持 `https` 方式访问 GitLab。
-
-下面的配置文件展示的是"tool file"的内容。
-
-关于更多关于DevStream的主配置、tool file、var file的信息，请阅读[核心概念概览](../core-concepts/overview.zh.md)和[DevStream配置](../core-concepts/config.zh.md).
-
-```yaml
---8<-- "gitlab-ce-docker.yaml"
-```
-
-## 一些可能有用的命令
-
-- 克隆项目
-
-```shell
-export hostname=YOUR_HOSTNAME
-export username=YOUR_USERNAME
-export project=YOUR_PROJECT_NAME
-```
-
-1. ssh 方式
-
-```shell
-# port is 22
-git clone git@${hostname}/${username}/${project}.git
-# port is not 22, 2022 as a sample
-git clone ssh://git@${hostname}:2022/${username}/${project}.git
-```
-
-2. http 方式
-
-```shell
-# port is 80
-git clone http://${hostname}/${username}/${project}.git
-# port is not 80, 8080 as a sample
-git clone http://${hostname}:8080/${username}/${project}.git
-```
diff --git a/docs/plugins/gitlab-ce-docker/gitlab-ce-images.txt b/docs/plugins/gitlab-ce-docker/gitlab-ce-images.txt
deleted file mode 100644
index 7759ed737..000000000
--- a/docs/plugins/gitlab-ce-docker/gitlab-ce-images.txt
+++ /dev/null
@@ -1,2 +0,0 @@
-##harbor-images
-gitlab/gitlab-ce:rc
diff --git a/docs/plugins/gitlab-ci.md b/docs/plugins/gitlab-ci.md
deleted file mode 100644
index 274f8ff52..000000000
--- a/docs/plugins/gitlab-ci.md
+++ /dev/null
@@ -1,22 +0,0 @@
-# gitlab-ci Plugin
-
-This plugin creates GitLab CI workflow.
-
-It downloads a template of your choice, renders it with provided parameters, and creates a GitLab CI file for your repo.
-
-## Usage
-
-The following content is an example of the "tool file".
-
-For more information on the main config, the tool file, and the var file of DevStream, see [Core Concepts Overview](../core-concepts/overview.md) and [DevStream Configuration](../core-concepts/config.md).
-
-Plugin config example:
-
-```yaml
---8<-- "gitlab-ci.yaml"
-```
-
-**Notes:**
-
-- `scm` config option represents codebase location; for more info, you can refer to [SCM Config](./scm-option.md).
-- The `pipeline` config option controls `CI` stages; you can refer to [Pipeline Config](./pipeline.md) for more info.
diff --git a/docs/plugins/gitlab-ci.zh.md b/docs/plugins/gitlab-ci.zh.md
deleted file mode 100644
index b13bb78f4..000000000
--- a/docs/plugins/gitlab-ci.zh.md
+++ /dev/null
@@ -1,15 +0,0 @@
-# gitlab-ci 插件
-
-该插件用于在使用 gitlab 的项目仓库中创建 Gitlab CI 并运行对应项目的 gitlab runner。
-
-### 配置项
-下面的内容是一个示例配置文件用于创建 Gitlab CI：
-
-``` yaml
---8<-- "gitlab-ci.yaml"
-```
-
-**注意:**
-
-- `scm` 配置字段用于表示代码仓库的配置信息，具体配置可查看[SCM配置项](./scm-option.zh.md)。
-- `pipeline` 选项项用于控制 `CI` 流程中的各个阶段，具体配置可查看文档[pipline配置项](pipeline.zh.md)。
diff --git a/docs/plugins/harbor-docker.md b/docs/plugins/harbor-docker.md
deleted file mode 100644
index 025209692..000000000
--- a/docs/plugins/harbor-docker.md
+++ /dev/null
@@ -1,13 +0,0 @@
-# harbor-docker Plugin
-
-// TODO(daniel-hutao): I'll add the docs here after Chinese docs be stable.
-
-## Usage
-
-The following content is an example of the "tool file".
-
-For more information on the main config, the tool file and the var file of DevStream, see [Core Concepts Overview](../core-concepts/overview.md) and [DevStream Configuration](../core-concepts/config.md).
-
-``` yaml
---8<-- "harbor-docker.yaml"
-```
diff --git a/docs/plugins/harbor-docker.zh.md b/docs/plugins/harbor-docker.zh.md
deleted file mode 100644
index 15f1ca95c..000000000
--- a/docs/plugins/harbor-docker.zh.md
+++ /dev/null
@@ -1,16 +0,0 @@
-# harbor-docker 插件
-
-TODO(daniel-hutao):
-- 支持 docker-compose 安装配置
-- 支持 https
-- 健壮性逻辑：判断机器上没有正在运行的 harbor
-
-## 用例
-
-下面的配置文件展示的是"tool file"的内容。
-
-关于更多关于DevStream的主配置、tool file、var file的信息，请阅读[核心概念概览](../core-concepts/overview.zh.md)和[DevStream配置](../core-concepts/config.zh.md).
-
-``` yaml
---8<-- "harbor-docker.yaml"
-```
diff --git a/docs/plugins/helm-installer/argocd.md b/docs/plugins/helm-installer/argocd.md
deleted file mode 100644
index 0718c6bff..000000000
--- a/docs/plugins/helm-installer/argocd.md
+++ /dev/null
@@ -1,26 +0,0 @@
-# Install Argo CD with DevStream
-
-## InstanceID Prefix
-
-The `instanceID` prefix must be `argocd`, the minimum tools configuration example:
-
-```yaml
-tools:
-- name: helm-installer
- instanceID: argocd
-```
-
-## Default Configs
-
-| key | default value | description |
-| ---------------- | ------------------------------------ | ------------------------------------------------ |
-| chart.chartPath | "" | local chart path |
-| chart.chartName | argo/argo-cd | chart name |
-| chart.version | "" | chart version |
-| chart.timeout | 10m | this config will wait 10 minutes to deploy Argo CD |
-| chart.upgradeCRDs | true | default update CRD config |
-| chart.releaseName | argocd | helm release name |
-| chart.namespace | argocd | namespace where helm to deploy |
-| chart.wait | true | whether to wait until installation is complete |
-| repo.url | https://argoproj.github.io/argo-helm | helm official repo address |
-| repo.name | argo | helm repo name |
diff --git a/docs/plugins/helm-installer/argocd.zh.md b/docs/plugins/helm-installer/argocd.zh.md
deleted file mode 100644
index d2cb41c9e..000000000
--- a/docs/plugins/helm-installer/argocd.zh.md
+++ /dev/null
@@ -1,26 +0,0 @@
-# 使用 DevStream 部署 Argo CD
-
-## 前缀匹配
-
-`instanceID` 的前缀需要是 `argocd`，最小化 tools 配置示例：
-
-```yaml
-tools:
-- name: helm-installer
- instanceID: argocd
-```
-
-## 默认配置
-
-| 配置项 | 默认值 | 描述 |
-| ---- | ---- | ---- |
-| chart.chartPath | "" | 本地 chart 包路径 |
-| chart.chartName | argo/argo-cd | chart 包名称 |
-| chart.version | "" | chart 包版本 |
-| chart.timeout | 10m | helm install 的超时时间 |
-| chart.upgradeCRDs | true | 是否更新 CRDs（如果有） |
-| chart.releaseName | argocd | helm 发布名称 |
-| chart.namespace | argocd | 部署的命名空间 |
-| chart.wait | true | 是否等待部署完成 |
-| repo.url | https://argoproj.github.io/argo-helm | helm 仓库地址 |
-| repo.name | argo | helm 仓库名 |
diff --git a/docs/plugins/helm-installer/artifactory.md b/docs/plugins/helm-installer/artifactory.md
deleted file mode 100644
index 3c8f3578c..000000000
--- a/docs/plugins/helm-installer/artifactory.md
+++ /dev/null
@@ -1,59 +0,0 @@
-# Install Artifactory with DevStream
-
-## InstanceID Prefix
-
-The `instanceID` prefix must be `artifactory`, the minimum tools configuration example:
-
-```yaml
-tools:
-- name: helm-installer
- instanceID: artifactory
-```
-
-## Default Configs
-
-| key | default value | description |
-| ---- | ---- | ---- |
-| chart.chartPath | "" | local chart path |
-| chart.chartName | jfrog/artifactory | chart name |
-| chart.timeout | 10m | this config will wait 10 minutes to deploy |
-| chart.releaseName | artifactory | helm release name |
-| chart.upgradeCRDs | true | default update CRD config |
-| chart.wait | true | whether to wait until installation is complete |
-| chart.namespace | artifactory | namespace where helm to deploy |
-| repo.url | https://charts.jfrog.io | offical helm repo address |
-| repo.name | jfrog | helm repo name |
-
-## Test/Local Dev Environment
-
-If you want to **test the plugin locally**， The following `valuesYaml` configuration can be used
-
-```yaml
-valuesYaml: |
- artifactory:
- service:
- type: NodePort
- nodePort: 30002
- nginx:
- enabled: false
-```
-
-In this configuration
-
-- Postgresql dependencies are automatically created.
-- local disks on machines in the cluster are defaulted used for data mounting.
-- Using `nodePort` to expose service, You can access `artifactory` by domain `http://{{k8s node IP}}:30002`. The default account name and password are admin/password (please replace the default account password in the production environment).
-
-## Production Environment
-
-### External Storage
-
-- PostgreSQL: Set the `database.url` to Postgresql's address. More info can be found in [Config](https://www.jfrog.com/confluence/display/JFROG/Configuring+the+Database).
-
-### Disk Storage
-
-You can set `customVolumes` and `customVolumeMounts` for this service. More info can be found in [Config](https://www.jfrog.com/confluence/display/JFROG/Configuring+the+Filestore).
-
-### Network Config
-
-This plugin support `Ingress`, `ClusterIP`, `NodePort` and `LoadBalancer` , You can give choice to your needs.
diff --git a/docs/plugins/helm-installer/artifactory.zh.md b/docs/plugins/helm-installer/artifactory.zh.md
deleted file mode 100644
index 3bc0c9d48..000000000
--- a/docs/plugins/helm-installer/artifactory.zh.md
+++ /dev/null
@@ -1,60 +0,0 @@
-# 使用 DevStream 部署 Artifactory
-
-## 前缀匹配
-
-`instanceID` 的前缀需要是 `artifactory`，最小化 tools 配置示例：
-
-```yaml
-tools:
-- name: helm-installer
- instanceID: artifactory
-```
-
-## 默认配置
-
-| key | default value | description |
-| ---- | ---- | ---- |
-| chart.chartPath | "" | 本地 chart 包路径 |
-| chart.chartName | jfrog/artifactory | chart 名称 |
-| chart.version | "" | chart 版本 |
-| chart.timeout | 10m | 等待部署成功的时间 |
-| chart.upgradeCRDs | true | 默认更新 CRD 配置（如果存在的话） |
-| chart.releaseName | artifactory | helm 发布名称 |
-| chart.namespace | artifactory | helm 部署的命名空间名称 |
-| chart.wait | true | 是否等待部署完成 |
-| repo.url | https://charts.jfrog.io | helm 官方仓库地址 |
-| repo.name | jfrog | helm 仓库名 |
-
-## 测试环境
-
-如果你想在**本地测试插件**， 可以使用如下 `valuesYaml` 配置。
-
-```yaml
-valuesYaml: |
- artifactory:
- service:
- type: NodePort
- nodePort: 30002
- nginx:
- enabled: false
-```
-
-在该配置下
-
-- helm 会自动创建依赖的 Postgresql；
-- 数据挂载的磁盘默认会使用集群上机器的本地磁盘；
-- 通过 `NodePort` 对外暴露服务，可使用 `http://{{k8s 节点ip}}:30002` 域名来访问，默认账号名密码为 admin/password (生产环境请替换默认账号密码)。
-
-## 生产环境
-
-### 外部存储
-
-- PostgreSQL：设置 `database.url` 来设置数据库地址，具体配置可参考 [Config](https://www.jfrog.com/confluence/display/JFROG/Configuring+the+Database) 中的选项。
-
-### 磁盘存储
-
-可以设置 `customVolumes` 和 `customVolumeMounts` 来配置挂载磁盘，具体配置可参考 [Config](https://www.jfrog.com/confluence/display/JFROG/Configuring+the+Filestore)。
-
-### 网络层配置
-
-该插件支持 `Ingress`, `ClusterIP`, `NodePort`, `LoadBalancer` 对外暴露的模式，可以基于需求进行选择。
diff --git a/docs/plugins/helm-installer/devlake.md b/docs/plugins/helm-installer/devlake.md
deleted file mode 100644
index 7cdcc1c79..000000000
--- a/docs/plugins/helm-installer/devlake.md
+++ /dev/null
@@ -1,26 +0,0 @@
-# Install DevLake with DevStream
-
-## InstanceID Prefix
-
-The `instanceID` prefix must be `devlake`, the minimum tools configuration example:
-
-```yaml
-tools:
-- name: helm-installer
- instanceID: devlake
-```
-
-## Default Configs
-
-| key | default value | description |
-| ---------------- | ------------------------------------ | ------------------------------------------------ |
-| chart.chartPath | "" | local chart path |
-| chart.chartName | "devlake/devlake | chart name |
-| chart.version | "" | chart version |
-| chart.timeout | 10m | this config will wait 10 minutes to deploy DevLake |
-| chart.upgradeCRDs | true | default update CRD config |
-| chart.releaseName | devlake | helm release name |
-| chart.namespace | devlake | namespace where helm to deploy |
-| chart.wait | true | whether to wait until installation is complete |
-| repo.url | https://apache.github.io/incubator-devlake-helm-chart | helm official repo address |
-| repo.name | devlake | helm repo name |
diff --git a/docs/plugins/helm-installer/devlake.zh.md b/docs/plugins/helm-installer/devlake.zh.md
deleted file mode 100644
index d2a36f1b7..000000000
--- a/docs/plugins/helm-installer/devlake.zh.md
+++ /dev/null
@@ -1,26 +0,0 @@
-# 使用 DevStream 部署 DevLake
-
-## 前缀匹配
-
-`instanceID` 的前缀需要是 `devlake`，最小化 tools 配置示例：
-
-```yaml
-tools:
-- name: helm-installer
- instanceID: devlake
-```
-
-## 默认配置
-
-| 配置项 | 默认值 | 描述 |
-| ---- | ---- | ---- |
-| chart.chartPath | "" | 本地 chart 包路径 |
-| chart.chartName | devlake/devlake | chart 包名称 |
-| chart.version | "" | chart 包版本 |
-| chart.timeout | 10m | helm install 的超时时间 |
-| chart.upgradeCRDs | true | 是否更新 CRDs（如果有） |
-| chart.releaseName | devlake | helm 发布名称 |
-| chart.namespace | devlake | 部署的命名空间 |
-| chart.wait | true | 是否等待部署完成 |
-| repo.url | https://apache.github.io/incubator-devlake-helm-chart | helm 仓库地址 |
-| repo.name | devlake | helm 仓库名 |
diff --git a/docs/plugins/helm-installer/harbor.md b/docs/plugins/helm-installer/harbor.md
deleted file mode 100644
index 6a43b19ca..000000000
--- a/docs/plugins/helm-installer/harbor.md
+++ /dev/null
@@ -1,149 +0,0 @@
-# Install Harbor with DevStream
-
-## 1 Prerequisites
-
-- An existing Kubernetes cluster, version > 1.10
-- StorageClass
-
-If you are sure you already have a StorageClass configured for your K8s cluster, you can [_skip this section and move on to the next_](#2-harbor-architecture).
-
-If you are uncertain about StorageClass, here's a bit more explanation:
-
-> Depending on the installation method, your Kubernetes cluster may be deployed with an existing StorageClass marked as default. This default StorageClass is then used to dynamically provision storage for PersistentVolumeClaims that do not require any specific storage class. See [PersistentVolumeClaim documentation](https://kubernetes.io/docs/concepts/storage/persistent-volumes/#persistentvolumeclaims) for details.
-
-Examples:
-
-- For local clusters created by `minikube,` there is already a default standard StorageClass using hostpath.
-- For local clusters created by `kind,` there is a default standard StorageClass using rancher.io/local-path.
-- For K8s-as-a-Service in public cloud providers, it's highly likely that a default StorageClass is created. For example, for AWS EKS, the default is gp2, using AWS EBS. Note that the pre-installed default StorageClass may not fit well with your expected workload; for example, it might provision storage that is too expensive. If this is the case, you can either change the default StorageClass or disable it thoroughly to avoid the dynamic provisioning of storage. For more information on this topic, see [the official doc here](https://kubernetes.io/docs/tasks/administer-cluster/change-default-storage-class/).
-
-## 2 Harbor Architecture
-
-
-
-## 3 Using the Harbor Plugin with DevStream
-
-### 3.1 Quickstart
-
-For a local testing and developing purpose, we can deploy Harbor quickly using the minimal config as follows:
-
-```yaml
-tools:
-- name: helm-installer
- instanceID: harbor-001
- dependsOn: [ ]
- options:
- valuesYaml: |
- externalURL: http://127.0.0.1
- expose:
- type: nodePort
- tls:
- enabled: false
- chartmuseum:
- enabled: false
- notary:
- enabled: false
- trivy:
- enabled: false
-```
-
-After running `dtm apply`, we can see the following resources in the "harbor" namespace:
-
-- **Deployment** (`kubectl get deployment -n harbor`)
-
-Most Harbor-related services run as Deployments:
-
-```shell
-NAME READY UP-TO-DATE AVAILABLE AGE
-harbor-core 1/1 1 1 2m56s
-harbor-jobservice 1/1 1 1 2m56s
-harbor-nginx 1/1 1 1 2m56s
-harbor-portal 1/1 1 1 2m56s
-harbor-registry 1/1 1 1 2m56s
-```
-
-- **StatefulSet** (`kubectl get statefulset -n harbor`)
-
-Harbor depends on Postgres and Redis, which are deployed as StatefulSets. Notice that these dependencies are not deployed to a production-ready level with highly-availability and redundancy.
-
-```shell
-NAME READY AGE
-harbor-database 1/1 3m40s
-harbor-redis 1/1 3m40s
-```
-
-- **Service** (`kubectl get service -n harbor`)
-
-By default, Harbor is exposed on port 30002 as type NodePort:
-
-```shell
-NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
-harbor NodePort 10.99.177.6
-
-
-
-!!! hint "提示"
-
- 跳转到B站观看清晰度更高。
-
-## 1、概述
-
-本文将介绍如何通过 DevStream 在本地部署 `GitLab + Jenkins + Harbor` 工具链，并且以 Java Spring Boot 项目为例，演示如何通过 DevStream 快速创建 Java Spring Boot 项目脚手架，同时在 Jenkins 上自动创建对应的 Pipeline 实现 Java Spring Boot 项目的 CI 流程。
-
-!!! hint "提示"
-
- 本文基于 kubeadm 部署的单节点 k8s 环境，不适用于 minikube 和 kind 等 docker-in-docker 类型的 k8s 集群。
-
-### 1.1、工作流介绍
-
-本文最终将实现的工具链相关工作流如下图所示：
-
-