Armel Soro 147542db69 Do not necessarily error out if odo dev is stopped via Ctrl+C (#6917) ...

* Add test highlighting the expectations

* Propagate errors and call os.Exit only in 'main' functions

See ExitInMain[1] and ExitInMain_ExitOnce[2] coding convention guidelines.

[1] https://github.com/redhat-developer/odo/wiki/Dev:-Coding-Conventions#exit-in-main
[2] https://github.com/redhat-developer/odo/wiki/Dev:-Coding-Conventions#exit-once

* Handle errors returned by Cleanuper#Cleanup

This makes sure the exit code of the command
is mapped onto any error returned by Cleanup

* Do not return an error when the watch loop in 'odo dev' is interrupted

* Test that the exit code of 'odo dev' matches the error returned by the cleanup logic

2023-06-22 13:14:07 +02:00

..

errors.go

Preference cleanup (1/n) (#5822)

2022-06-23 14:27:39 +00:00

implem_test.go

Bump Go to 1.19 (#6586)

2023-02-16 09:03:48 -05:00

implem.go

Do not necessarily error out if odo dev is stopped via Ctrl+C (#6917)

2023-06-22 13:14:07 +02:00

machine_output.go

Allow using imageName as a selector (#6768)

2023-05-22 10:45:27 -04:00

mock.go

Allow using imageName as a selector (#6768)

2023-05-22 10:45:27 -04:00

preference.go

Allow using imageName as a selector (#6768)

2023-05-22 10:45:27 -04:00

variables.go

Allow using imageName as a selector (#6768)

2023-05-22 10:45:27 -04:00