-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[exporter/file] Support setting permissions on opened files #31459
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Pinging code owners for pkg/stanza: @djaglowski. See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Hi,@sinkingpoin~I concur with the proposal to incorporate a configuration option into the file exporter for setting the permissions bits. Concurrently, I believe that the user/group associated with the file should be granted read-only permissions. |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This issue has been closed as inactive because it has been stale for 120 days with no activity. |
Component(s)
exporter/file
Is your feature request related to a problem? Please describe.
Currently, all files opened by the file exporter are opened with 0600 (https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/pkg/stanza/operator/output/file/file.go#L80). This precludes anything except the user that the collector is running on from reading the files that it outputs. I want to be able to configure that, so that we can have more finely grained permissions.
Describe the solution you'd like
I want to add a configuration option to the file exporter to allow setting the permissions bits, and the user/group of the file that the file exporter makes. This configuration should be generic enough that it can be used in other file-like exporters (see: namedpipeexporter)
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: