File.Contents prints whole file in log

[vague notch]

Hi, I read a file from a directory (module written in golang) using:

content, err := someDirectory.File(“foo.txt”).Contents(ctx)

The problem I am facing now is that the whole content of the file is shown in the dagger log output and dagger.cloud. In case such a file contains secrets they will be revealed and send to dagger.cloud.
Along with the security problem it pollutes the logs. If I want to show the content of the file, I would do it with an extra option or command.

Is there a way to stop dagger from sending file content to the logs and to dagger.cloud?

I would be happy to get some ideas.

Thanks
Dominik

File.Contents prints whole file in log

[tulip socket]

@vague notch we don't advise sending files with sensitive to the build pipeline as those will be stored in the dagger cache without any proper masking.

When dealing with secrets, it's generally advisable to pass them to your function as a dagger.Secret type. Here's more info about it: https://docs.dagger.io/features/secrets/

[vague notch]

Hi, agree, no secrets should be passed in files to the build pipeline.
Are there ideas to pass an env file which is treated as secrets? That would help a lot in managing multiple secrets more dynamically.