You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Proposal: Adding a docker_command package type to the Aqua toolchain.
Whalebrew provides a cli experience to invoke dockerized commands. However, it was more clunky than I'd like. But there seems to be a lot of interest in the project in the past. People working with mixed toolchains would like to have tools that don't have static binaries contained in a docker image. For example, the AWS CLI requires running Python install commands, and conflicts between version one and two could occur. Using a docker image solves those concerns.
My proposal is to add a new package type called docker_command to the Aqua toolchain. This would allow users to invoke CLI commands that Aqua proxy resolves since it was shimmed. Here's an example of how this could work:
- name: [email protected]
registry: local
args_docker_custom: []
args_cli_custom: []
Invoke aws would then be aqua proxy constructing that docker command with volume mounts and such so it works be transparent and function like a normal cli.
This feature would let me use Aqua to manage and pin dockerized tools in the same wonderful experience I get through Aqua. This would eliminate clunky shell aliases trying to accomplish the same thing and benefit from the same version pinned and managed process aqua currently provides.
When a package is executed, Whalebrew will run the specified image with Docker, mount the current working directory in /workdir, and pass through all of the arguments.
So whalebrew can't read and write files outside of the current directory.
Proposal: Adding a
docker_command
package type to the Aqua toolchain.Whalebrew provides a cli experience to invoke dockerized commands. However, it was more clunky than I'd like. But there seems to be a lot of interest in the project in the past. People working with mixed toolchains would like to have tools that don't have static binaries contained in a docker image. For example, the AWS CLI requires running Python install commands, and conflicts between version one and two could occur. Using a docker image solves those concerns.
My proposal is to add a new package type called
docker_command
to the Aqua toolchain. This would allow users to invoke CLI commands that Aqua proxy resolves since it was shimmed. Here's an example of how this could work:Invoke
aws
would then be aqua proxy constructing that docker command with volume mounts and such so it works be transparent and function like a normal cli.This feature would let me use Aqua to manage and pin dockerized tools in the same wonderful experience I get through Aqua. This would eliminate clunky shell aliases trying to accomplish the same thing and benefit from the same version pinned and managed process aqua currently provides.
Reference
The text was updated successfully, but these errors were encountered: