Experiment with dagger SDK/Mage for running registry and test tasks #2576
Replies: 1 comment 2 replies
-
Thank you for your proposal. We use cmdx, shell scripts, registry-tool, and Docker to build aqua-registry's local development workflow.
So in my understanding, your proposal is to replace them with Dagger or Mage. Is this correct? Indeed, current cmdx tasks and shell scripts depend on bash and environment so I wanted to migrate parts of them to registry-tool. BTW, we ever used Earthly but stopped using it as Earthly was a little slow and the current implementation with cmdx and Docker was faster and better experience than Earthly. aquaproj/aqua-registry#16597 |
Beta Was this translation helpful? Give feedback.
-
Overview
Dagger runs containerized. Runs equally well on a windows machine, macOS, or Linux, and would allow Go based test and configuration runs without any environment impact.
Why is the proposal needed?
I noticed the cmdx tool is used which is pretty cool (reminds me of Task).
Consider using Mage as an alternative to experiment with which would let you eliminate any core reliance on shell scripts for automation.
Note
I'm not asking you to go do it, rather if you'd be open a to demo magefile contribution that could include automating some of the tasks that use containers and a few supporting tasks as a start.
It's not high priority, but if interested I'd be glad to demo something.
I've used for over 2 years and found it great for automation in nearly 100% Go, while being low friction. The Dagger SDK provides another level of amazing automation capabilities that isolate the system from being impacted by the environment, perhaps improving long term maintenance.
Beta Was this translation helpful? Give feedback.
All reactions