#default secret
1 messages · Page 1 of 1 (latest)
No, right now secrets need to be passed in explicitly. Can you share more details about your use case and desired behavior?
I've got some auth tokens for various services in an OpenTofu pipeline, and I don't want to have to pass them in as --foo-token=env:FOO_TOKEN for every call. This pipeline will be used on dev laptops, and I want to be able to cleanly say "set up your environment and then run dagger call plan" or similar.
Thanks for sharing, yeah makes perfect sense. This is an area that could use some polish for sure.
There is an existing issue to track this, I think its the same as your use case: https://github.com/dagger/dagger/issues/8286
There is always a balance we're trying to reach between having reproducible builds that don't rely on any "magic" files or values floating around somewhere, and the end user experience being too cumbersome.