compose

Commit Graph

Author	SHA1	Message	Date
Guillaume Tardif	adeba9b124	Fix bug not allowing users to run any context command when set to an aws context type. When users have an “aws" context type, we try to exec the command (will execute context ls, context use, etc.) and when it fails because it doesn’t find the aws backend, then display the custom error for aws context type. Signed-off-by: Guillaume Tardif <guillaume.tardif@docker.com>	2020-09-04 11:01:55 +02:00
Chris Crone	4c6280b0e9	Rename docker/api -> docker/compose-cli Signed-off-by: Chris Crone <christopher.crone@docker.com>	2020-08-21 17:28:39 +02:00
Chris Crone	f8ce7a4780	cli: Move to gotest.tools Signed-off-by: Chris Crone <christopher.crone@docker.com>	2020-08-04 14:03:24 +02:00
Djordje Lukic	ad72c866cc	Add license headers	2020-06-18 16:48:03 +02:00
Guillaume Tardif	98f7a8e1aa	When can not load config file, the previous cli is displaying a WARNING message, but continues with default context, we should do the same. This happened in some desktop e2e tests where the config file is not set properly in WSL2 environment, see https://github.com/docker/pinata/pull/14062	2020-06-15 11:41:26 +02:00
Djordje Lukic	22d4d250a9	Move the config into own package and outside of cli	2020-06-08 16:01:36 +02:00
Guillaume Tardif	e2b9f5bc57	Move login to root command, delegate to classic login when only one arg and not dot in it	2020-06-01 22:55:46 +02:00
Christopher Crone	7e81f9e147	Appease linter Signed-off-by: Christopher Crone <christopher.crone@docker.com>	2020-05-18 15:12:52 +02:00
Christopher Crone	f6fcd27a09	Factor determination of current context Signed-off-by: Christopher Crone <christopher.crone@docker.com>	2020-05-18 14:40:15 +02:00

9 Commits