#Zenith extensions
1 messages · Page 1 of 1 (latest)
I’ll start:
- Matt’s ultimate go builder : https://twitter.com/mattjamesboyle/status/1689536391087034368
- I think a Github Actions extension with functions to natively run GHA jobs, backed by @shadow kettle Project Gale, could now be implemented!
- @rancid egret showed a POC of daggerized Pulumi. That could be the start of a Pulumi extension
Lots of potential to make integration testing easier with environments.
E.g. a Postgres environment could set up a containerized postgres service for use in integ tests
Ditto any sort of "infra" you might want to run locally. E.g. dagger internally uses minio as a local S3 replacement for integ tests, could have a minio environment for setting that up (it's kind of a pain, would be happy to delete that code from our tests and just use an env instead)
If we‘re talking about integration testing kind or any other k8s provider would make sense as well
Agreed about postgres and minio those are good examples
I think in general just about any build system could be wrapped up into env too.
CMake comes to mind right away, just because whenever I have to interact with it I am always googling trying to remember how to configure various things.
Secret providers (i.e. give me secrets sourced from Vault, temporary AWS tokens from a credential provider, etc.) will be great. Still need to figure out the exact model, but should make a ton sense to use environments for this.
👆 this could be tricky but if we could find a way to integrate, that would be really useful
Agreed, we haven't really explored how this would work yet, and obviously anything involving security needs extra scrutiny, but we'll figure it out in time 🙂
If I can build, run, and debug my apps using this, I will gladly use it on a daily basis.
"debug" specifically made me think we should add a Shell environment for various debuggers; i.e. open a gdb shell attached to a binary, delve, etc.
@hazy notch would it make sense to support exposing certain parts of an extension in the parent environment, from the json config - ie. without having to write pass-through code?
I think we discussed that during the zenithathon
Yes for sure, still need to add WithExtension functionality, but once it's in place it's trivial to support it in code, in dagger.json, or both
Can I already load an environment dynamically in code?
Yes, WithExtension would just be sugar that loads the other env up and calls With* on your environment using the other environments entrypoints, but it's possible to do this today by hand
Sourcegraph: #daggernauts message
Infisical for secrets management? https://github.com/Infisical/infisical
With @safe dawn exploring Tekton/Dagger compatibility, I think a Tekton extension would be a great candidate 🙂
FYI @broken narwhal you'll probably be interested in this thread
Docker Compose support... thanks to @icy rivet 🙂 https://github.com/vito/dagger-compose