The module's container (technically that

[idle wolf]

Got it, so the current way to handle this is something like:
dagger call --aws-credentials-file file:~/aws/credentials --aws-config-file file:~/aws/config

[limpid spear]

yes that's right.

[idle wolf]

I noticed the same for environment variables as well. So no host system components can 'leak' into modules. I see the benefit of this yes. The price of course is verbosity

[limpid spear]

Right. you can make it less obnoxious by shortening argument names, but until we add the convenience layer, that's the UX we have for now.

Totally worth it in the long run 🙂 The Dagger software ecosystem will be safer and more useful.

[idle wolf]

Makes sense. Do the new docs point out this locking down of 'ambient system access'? I definitely was quite confused at what my module was pointing to and why I couldn't pull from host env until we had this discussion

[limpid spear]

cc @past epoch @sour wharf

the answer is probably "not yet" 🙂 that's great feedback

[past epoch]

there is a note in step 3 of this guide that mentions it https://docs.dagger.io/zenith/guides/457482/create-app-ci-module#step-3-add-a-function-to-test-the-application but we could probably make it more prominent

[sharp mango]

It's also in https://docs.dagger.io/zenith/developer-guide/overview/942201/execution-environment

[idle wolf]

latter was exactly what I was looking for, thanks yall