Use subcommands for example/cli about deploykit HOT 5 CLOSED

It does appear overly-complicated at first glance, but the separate commands are an artifact of the plugin-oriented nature of InfraKit. Since plugins are daemons that communicate via sockets, they are built and executed independently. Without language-level support for dynamic library loading, i'm not sure there's a better way. Any ideas?

from deploykit.

@wfarner You could use git-style sub-command resolution.

from deploykit.

@stevvooe not a good fit here, since plugins will be coming from different build sources, and can't be expected to be placed in the same directory.

from deploykit.

@wfarner Git doesn't require this. It just does a search through a path variable. They don't need to be in the same directory. exec.LookPath actually searches all paths. So, if you're using two projects, you just do PATH=$PROJ_ONE_PATH:$PROJ_TWO_PATH.

from deploykit.

Capturing offline discussion with @stevvooe, a CLI-oriented flow won't work well across plugin boundaries as it would require CLI-specific APIs for plugin communication (e.g. surfacing help text, arguments, output, etc). The long-term goal is to delegate plugin management to the environment InfraKit is used in. For example, in Docker Engine we will provide scaffolding to run them as Docker plugins.

from deploykit.