Daijiro Fukuda

Sorry we have not been able to respond. It may take some time, but we will.

So you need to configure [s3_bucket](https://docs.fluentd.org/output/s3#s3_bucket) dynamically from the actual records. I don't think there is any good way for this. :cry: We need to implement it. If the patterns...

@Athishpranav2003 Thanks! I'm seeing this. > Ideally we would need `"{\"Authorization\":\"Bearer #{ENV['TEST_PORT']}\"}"` to be passed to json parser. I am checking if there is a clean way to make sure...

Thanks! I see! I'm seeing #4580.

We need to consider this as an issue of [Embedded Ruby Code](https://docs.fluentd.org/configuration/config-file#embedded-ruby-code). Using environment variables is just one way of it. `Embedded Ruby Code` feature is implemented in `LiteralParser`: https://github.com/fluent/fluentd/blob/e763c0761c44d9734b6aa374371387a2e8406522/lib/fluent/config/literal_parser.rb#L183-L199...

The logic of `literal_parser.rb` is for the very early stage of parsing. At this stage, there is no need to consider [the type of each config param](https://docs.fluentd.org/plugin-development/api-config-types). The reason is...

@pierreact Thanks for your report! We will check this soon.

@pierreact We found that, at least as a Ruby specification, Encoding::CompatibilityError occurs if the target data and the regular expression encoding do not match. In Fluentd, if we specify a...

Thanks @pierreact, @Watson1978 ! Looks like this is a general issue of Fluentd: * parser_regexp: cannot use non-ascii characters for regexp without setting encoding (There seems to be a similar...

Reopen. This can be a bug in `in_tail`. https://docs.fluentd.org/input/tail#encoding-from_encoding > If encoding is specified, in_tail changes string to encoding. Looks like this specification is broken since * #1409