Fork providers
Some original DevPod providers are not yet forked into the community fork:
Those that are deemed not dead should be forked and configured, and their releases published.
Configure providers uniformly
There are some irregularities in the configuration of the providers that are already forked.
In Taskfile.yaml, build:provider:dev depends on build:cli, but build:provider:release does not; it probably should.
What is called build:cli is called cli:build in the main DevPod repository, which seems inconsistent.
All task names in Taskfile.yaml start with build:, which seems redundant.
Taskfile.yaml is set up differently from the way it is done for the aws provider; assuming there is no reason for those differences, their configurations should be brought into alignment.
Unlike the aws and ssh providers, gcloud does not have .golangci.yaml file. - it does now
Does not have Taskfile.yaml.
Github workflows are different from the arrangement used for aws and gcloud.
Does not have:
- Taskfile.yaml
- .golangci.yaml
- .goreleaser.yml
- .mega-linter.yml
- .pre-commit-config.yaml
- renovate.json
- requirements.txt
Github workflows are different from all the other providers.
Clean up providers
Things that are done to the main DevPod code (e.g., proper handling of the CobraCommand Context) should be done to the forked providers.
Machine providers should add handling for machine describe.
Fork providers
Some original DevPod providers are not yet forked into the community fork:
Those that are deemed not dead should be forked and configured, and their releases published.
Configure providers uniformly
There are some irregularities in the configuration of the providers that are already forked.
aws
In
Taskfile.yaml,build:provider:devdepends onbuild:cli, butbuild:provider:releasedoes not; it probably should.What is called
build:cliis calledcli:buildin the main DevPod repository, which seems inconsistent.All task names in
Taskfile.yamlstart withbuild:, which seems redundant.gcloud
Taskfile.yamlis set up differently from the way it is done for theawsprovider; assuming there is no reason for those differences, their configurations should be brought into alignment.Unlike the- it does nowawsandsshproviders,gclouddoes not have.golangci.yamlfile.ssh
Does not have
Taskfile.yaml.Github workflows are different from the arrangement used for
awsandgcloud.kubernetes
Does not have:
Github workflows are different from all the other providers.
Clean up providers
Things that are done to the main DevPod code (e.g., proper handling of the CobraCommand Context) should be done to the forked providers.
Machine providers should add handling for
machine describe.