System config: add umask option

[daipom]

Is your feature request related to a problem? Please describe.

Some users need to change umask.
Example:

• File permissions can't have full accesss #4810

Currently, we have to use the command line option --umask.
It is inconvenient for the service or container image.

Describe the solution you'd like

Add umask option to the System config.

Describe alternatives you've considered

Without this option in System config, we can customize the command line options like #4810 (comment), but it is inconvenient.

Additional context

No response

[daipom]

It would be necessary for us to handle the following PR first:

• chumask: fix issue where it only works with standalone worker #4836

[blazethunderstorm]

@daipom can i work on this

[daipom]

@blazethunderstorm Thanks! Sure!

[daipom]

#4822 (comment)

I have found that this issue is a little complicated.
Let me summarize this issue.

• Before chumask: fix issue where it only works with standalone worker #4836, the files created by Fluentd are basically affected by the system's default umask value.
  • You can set those permissions by file_permission, but they are affected by the umask value as well.
  • Fluentd has --umask command line option, but it only worked when using --no-supervisor.
• After chumask: fix issue where it only works with standalone worker #4836, --umask command line option works when using --daemon as well.
  • In addition, when using --daemon, the default umask value becomes 0. So file_permission setting should now be fully applied.
  • --daemon:
    • This is true if you use fluent-package (or td-agent).
    • If you use the Docker images, this is not true. So chumask: fix issue where it only works with standalone worker #4836 is not relevant. We need another workaround.
• Add umask option to Fluentd system configuration & Fix Tests #4829:
  • It is great to allow that setting in system-config as well as in command line options.
  • However, if chumask: fix issue where it only works with standalone worker #4836 does not solve your issue (For example, you are using Docker images, etc.), it will not solve your issue.

[daipom]

#4810 (comment)

• ..., it would not work for Fluentd Docker images.
  • In ServerEngine, it appears that the umask value is applied only when using daemonize.
  • So, it would work for fluent-package, but not for Docker images.

I wonder why ServerEngine has such specifications.
Is there any reason why an application should not change umask if it does not run as a daemon?
If there is no particular reason, then we could fix ServerEngine to solve this issue.

Or is it possible to change umask on the container environment?