Ian Campbell 0b794e0620 e2e/cli-plugins: explicitly check that PersistentPreRunE works ... I regressed this in d4ced2ef77 ("allow plugins to have argument which match a top-level flag.") by unconditionally overwriting any `PersistentRunE` that the user may have supplied. We need to ensure two things: 1. That the user can use `PersistentRunE` (or `PersistentRun`) for their own purposes. 2. That our initialisation always runs, even if the user has used `PersistentRun*`, since that will shadow the root. To do this add a `PersistentRunE` to the helloworld plugin which logs (covers 1 above) and then use it when calling the `apiversion` subcommand (which covers 2 since that uses the client) Signed-off-by: Ian Campbell <ijc@docker.com>		2019-03-14 14:20:19 +00:00
..
docker-badmeta-err.golden	Add some simple e2e tests for executing CLI plugins	2019-01-30 13:44:05 +00:00
docker-help-badmeta-err.golden	Integrate CLI plugins with `docker help «foo»`	2019-01-30 13:45:18 +00:00
docker-help-helloworld-goodbye.golden	Integrate CLI plugins with `docker help «foo»`	2019-01-30 13:45:18 +00:00
docker-help-helloworld.golden	e2e/cli-plugins: explicitly check that PersistentPreRunE works	2019-03-14 14:20:19 +00:00
docker-help-nonexistent-err.golden	Integrate CLI plugins with `docker help «foo»`	2019-01-30 13:45:18 +00:00
docker-nonexistent-err.golden	Add some simple e2e tests for executing CLI plugins	2019-01-30 13:44:05 +00:00