Blueprints + local defaults = 🔥 | Dagger | Page 1

fallow oyster Sep 16, 2025, 9:29 PM

#

Is there an issue where I can read about the design of this new feature?

cloud patrol Sep 16, 2025, 9:30 PM

#

Yes, see #1413254056188579901 for ongoing discussion with testers, and this PR: https://github.com/dagger/dagger/pull/11034

GitHub

Local defaults by shykes · Pull Request #11034 · dagger/dagger

Load default module configuration from .env, to avoid typing too many CLI arguments on every call.
How it works

To persist default configuration for your dagger modules (typically secrets), write ...

cloud patrol Sep 16, 2025, 9:49 PM

#

(I just updated the PR description)

fading dagger Sep 16, 2025, 10:45 PM

#

This is A-MA-ZING! 🙂 🎉 daggerfire 🎉 🎉

cloud patrol Sep 16, 2025, 10:48 PM

#

Blueprints + local defaults = 🔥

fading dagger Sep 19, 2025, 7:57 AM

#

@cloud patrol , do you think this would be shipped in the next Release?
I am holding back so many refactors across our org to onboard them into blueprints, just because the experience would be SO MUCH better with a .env dropped by the side of the dagger.json... !!! 🙂

Asking so I may delay onboarding the teams into blueprints until .env is available if it's ~2 weeks

cloud patrol Sep 19, 2025, 8:23 AM

#

fading dagger <@488409085998530571> , do you think this would be shipped in the next Release? ...

Yes 2 weeks max. I'm aiming for 1 week but better safe than sorry 🙂

#Blueprints + local defaults = 🔥