Module initialization parameters + checks

[copper mauve]

I have a module that has a New function with a required parameter.
I can do dagger -m module --param=1 call ...
But I can't do dagger -m module --param=1 checks
Is this by design?

Also is there some standard way to initialize a module besides +default= pragmas?
Something that can run unsafe code like looking up env vars for secrets etc.

I'm currently using a script that figures out the parameters before invoking dagger, but then checks doesn't work.

[ebon bane]

you can configure "user defaults" in a .env file, for example:

MYMOD_PARAM=1

[copper mauve]

This feature flew under my radar. Took me a while to figure out, but it works!
Thank you.
What about the check command, shouldn't it allow passing constructor args to the module?
btw I see that 0.19.8 renamed checks to check, but I think the shell still has checks?

[ebon bane]

we haven't documented them yet... they are still experimental. but IMO ready to go stable