Closed rholshausen closed 1 year ago
However, I don't think this is useful. By default, it will install any plugin into the container, which is not what anyone would want. Users will need to mount the plugin installation directory and then set an environment variable just to get it to work. And it will then only install the Linux version of the plugins.
Ah, but you're forgetting about the next feature request "how can I run the plugin inside docker?" :trollface:.
So yes, this doesn't exactly feel useful.
The more and more we do this, the more I'm seeing the value in replacing our Ruby CLI with a cross-compilable one (e.g. Rust) that can be easily installed across most OS/Arch combinations, and downloaded via the common curl getpact.sh | bash
type thing.
Is there any value in merging this? For example, if flags could be passed to the plugin CLI (in a future change) to override the OS/Arch would that make this useful?
I think we don't add it until someone asks for it.
I think we close it for now. The only way I think we could make it work is:
~/.pact
directory (or again, provide a flag to specify another mapped volume mount)
This adds the plugin CLI into the docker image.
However, I don't think this is useful. By default, it will install any plugin into the container, which is not what anyone would want. Users will need to mount the plugin installation directory and then set an environment variable just to get it to work. And it will then only install the Linux version of the plugins.