- Jira-GitHub, Jira-GitLab integration
- Jenkins-GitHub, Jenkins-GitLab integration
- HashiCorp Vault
- 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
Check plugin(s)' state.
This is already supported, but we will improve the features of it, for example:
- show the default config of one plugin
- show the default configs of multiple plugins that are used together
- interactive: user select plugin then show the default config
Background: currently, we use GitHub releases to store pre-built binaries and plugins. We might need to figure out a better way to store/distribute plugins and binaries.
- Consider AWS S3 or similar choices for plugin storage.
- Make sure people who don't have optimum internet connections (e.g., users behind firewall or proxy) can still use DevStream smoothly.
- AWS EC2 (linux-amd64) creation with Terraform/Ansible
- Push notification to Slack/Lark when the testing environment is occupied or released
- 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
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