#Ko & Cosign integration
1 messages · Page 1 of 1 (latest)
We are not planning to integrate the core of Dagger with those tools, but the number one feature in development are containerized, cross-language functions, that can be packaged in reusable modules. You can use these functions to wrap any tool you want, as long as they can run in a container, and the inputs and outputs you need can be expressed in Dagger's type system. So a Ko and Cosign integration would most likely happen that way.
@errant helm may I ask if you have a specific use case in mind for Dagger?
i am almost going towards replacing make with dagger. i have to restrain myself because the force is strong with this tool 🙂
If you're into the bleeding edge, check out https://daggerverse.dev look at the list of modules, and imagine a module called "Ko" or "Cosign". That's probably what it would look like