devspace-sh/devspace

DevSpace - The Fastest Developer Tool for Kubernetes ⚡ Automate your deployment workflow with DevSpace and develop software directly inside Kubernetes.

devspace's Issues

Add command: devspace add sync --local=XXX --remote=XXX

Init: allow to add multiple ports (comma-separated)

Delete build pod warning

[ERROR] Failed delete build pod
pods "devspace-build-rbtlc" not found

Save stacktrace information for errors

Currently no stacktrace is available for non panic errors. We should use a library like juju/errors to handle this functionality for us.

Add command: devspace add port --local=XXX --remote=XXX

Add command: devspace upgrade

This command should replace the devspace executable file with the newest release.

Add command: devspace remove sync --local=XXX --remote=XXX

Add documentation

General setup:

• integrate docusaurus
• setup docs with devspace
• setup netlify for docs

To document:

• devspace init
• devspace up
• architecture
• getting started
• setup minikube
• devspace upgrade

Automate builds

Automate builds as far as possible. Code signing will have to remain manual.

Add command: devspace reset

Clean up everything by default:

• Call devspace down
• Delete registry release (not if --registry=false)
• Remove chart/ from project (not if --chart=false)
• Remove Dockerfile from project (not if --dockerfile=false)
• Remove .devspace/ from project (not if --config=false)

Add timeout for programming language detection

When calling devspace init, we try to auto-detect the programming language. This detection should be aborted after 10 seconds and show a preliminary result instead of running for a long time for big projects.

Programming language selection: plain

1. Ask user for base image (default: ubuntu:X)
2. Write Dockerfile with "FROM ubuntu:X)

Add command: devspace status

Detect when image building fails

Detect when kaniko fails building the Docker image, print the error and stop execution.

Add command: devspace status sync

Linux builds

Define the build process for creating executables for Linux

Detect if DevSpace pod has issues starting

Common case: image pull error
Use kubectl get and describe to get status and show it to the user

Add documentation to: cmd/init.go

Allow push to custom container registry (e.g. google container registry)

Check for kubernetes connection

Problem: When Kubernetes API server is not reachable, running devspace up will try to deploy tiller and gets stuck.

Solution: Check for Kubernetes API server connection before continuing.

Add command: devspace add package [package]

LoadingText: Append "(Xs)" to indicate how long the operation has been loading

Add command: devspace list sync

Handle failed helm release for internalRegistry

Check for failed release when registry installation does not complete successfully.
Inform user about failed releases (print reason) and ask if helm del --purge should be executed before retrying.

After re-building image: do not immediately use already running pod

Wait for old pod to enter "terminating" stage, then wait for new pod to enter "running" before starting port-forwarding, sync and terminal session

Add installer script for Linux

Add command sync status

v1.Config.DevSpace.SyncConfig.ExcludePaths/DownloadExcludePaths/UploadExcludePaths

• Make design decision regarding ignorefile vs config @FabianK1991
• Change code
• Add documentation

Add flag to devspace up: --no-sleep

--no-sleep should prevent overwriting the entrypoint/command for the container

Add README.md for docs/

• Development Guide
• Link to production env

Increase test coverage

Do not PANIC on wrong flag or wrong command

devspace -version currently leads to PANIC:

goroutine 1 [running]:
github.com/covexo/devspace/vendor/github.com/Sirupsen/logrus.Entry.log(0xc0420be870, 0xc042507290, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...)
        D:/Programmieren/go-workspace/src/github.com/covexo/devspace/vendor/github.com/Sirupsen/logrus/entry.go:126 +0x2d9
github.com/covexo/devspace/vendor/github.com/Sirupsen/logrus.(*Entry).Panic(0xc042718320, 0xc0426f7f50, 0x1, 0x1)
        D:/Programmieren/go-workspace/src/github.com/covexo/devspace/vendor/github.com/Sirupsen/logrus/entry.go:194 +0xb1
github.com/covexo/devspace/vendor/github.com/Sirupsen/logrus.(*Logger).Panic(0xc0420be870, 0xc0426f7f50, 0x1, 0x1)
        D:/Programmieren/go-workspace/src/github.com/covexo/devspace/vendor/github.com/Sirupsen/logrus/logger.go:244 +0x74
github.com/covexo/devspace/cmd.Execute()
        D:/Programmieren/go-workspace/src/github.com/covexo/devspace/cmd/root.go:28 +0x87
main.main()
        D:/Programmieren/go-workspace/src/github.com/covexo/devspace/main.go:10 +0x29```

Refactor logutil

Exiting terminal sometimes results in panic

[PANIC] Unable to start terminal session
command terminated with exit code 130
panic: (*logrus.Entry) (0x1825800,0xc042100be0)

goroutine 1 [running]:
github.com/covexo/devspace/vendor/github.com/Sirupsen/logrus.Entry.log(0xc0420b27d0, 0xc0434ba810, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0xc000000000, ...)
        C:/Users/gente/go/src/github.com/covexo/devspace/vendor/github.com/Sirupsen/logrus/entry.go:126 +0x2d9github.com/covexo/devspace/vendor/github.com/Sirupsen/logrus.(*Entry).Panic(0xc042100410, 0xc044693b98, 0x1, 0x1)
        C:/Users/gente/go/src/github.com/covexo/devspace/vendor/github.com/Sirupsen/logrus/entry.go:194 +0xb1
github.com/covexo/devspace/cmd.(*UpCmd).enterTerminal(0xc0427270a0)
        C:/Users/gente/go/src/github.com/covexo/devspace/cmd/up.go:626 +0x189
github.com/covexo/devspace/cmd.(*UpCmd).Run(0xc0427270a0, 0xc0428c2780, 0x29c7f18, 0x0, 0x0)
        C:/Users/gente/go/src/github.com/covexo/devspace/cmd/up.go:180 +0x1f3
github.com/covexo/devspace/cmd.(*UpCmd).Run-fm(0xc0428c2780, 0x29c7f18, 0x0, 0x0)
        C:/Users/gente/go/src/github.com/covexo/devspace/cmd/up.go:89 +0x59
github.com/covexo/devspace/vendor/github.com/spf13/cobra.(*Command).execute(0xc0428c2780, 0x29c7f18, 0x0, 0x0, 0xc0428c2780, 0x29c7f18)
        C:/Users/gente/go/src/github.com/covexo/devspace/vendor/github.com/spf13/cobra/command.go:766 +0x2c8
github.com/covexo/devspace/vendor/github.com/spf13/cobra.(*Command).ExecuteC(0x29959a0, 0x0, 0x1985ff9, 0x2b)
        C:/Users/gente/go/src/github.com/covexo/devspace/vendor/github.com/spf13/cobra/command.go:852 +0x311
github.com/covexo/devspace/vendor/github.com/spf13/cobra.(*Command).Execute(0x29959a0, 0x0, 0x148c646)
        C:/Users/gente/go/src/github.com/covexo/devspace/vendor/github.com/spf13/cobra/command.go:800 +0x32
github.com/covexo/devspace/cmd.Execute()
        C:/Users/gente/go/src/github.com/covexo/devspace/cmd/root.go:27 +0x34
main.main()
        C:/Users/gente/go/src/github.com/covexo/devspace/main.go:10 +0x29

Add command: devspace down

Shutdown DevSpace:

• Delete DevSpace release

Add documentation to cmd/up.go

Add flag: devspace up -r

-r   --restart    Restarts the deployed pods / containers (default: true)

Resolve go-lint warnings

Improve README

• Demo (asciinema.org?)
• Features
• Documentation
• Contributing > Reporting Issues
• Contributing > Contributing Code
• Contributing > Feedback & Feature Requests
• License

Use local docker daemon to build images

Add command: devspace list port

Integrate automatic tests into travis ci pipeline

Add command: devspace remove port --local=XXX --remote=XXX

Add command: devspace remove package [package]

Do not log portforwarding messages to stdout/stderr

Prettify Console Output

Automatically create namespace if it does not exist

relevant for:

• tiller server deployment
• devspace release

Make namespace configurable for port forwarding and sync

Currently the release namespace is automatically assumed for sync and port forwarding config, however it would be nice if we could sync files and forward ports from other namespaces as well.

Mac builds

Define the build process for creating executables for Mac

During image building show waiting message