David Venable

This issue came up in the community meeting yesterday. It sounds like the plan is to remove the terms "blacklist" and "whitelist" in 2.0. The `reindex.remote.whitelist` setting has been around...

Thank you for the response. For additional information, here is a snippet from where we do our configuration. You can see that our log line "Setting non-secure port to {}"...

Thanks for proposal. Yes, this would be helpful. Regarding the idea of using an array, I believe this is also best for OpenSearch documents. It should be easier to query...

This is actually the preferred version for Gradle 7, which Data Prepper now uses. https://github.com/jk1/Gradle-License-Report#usage

@ryn9, Thanks for the feedback. This proposal does not include conditionals any more complicated than skipping a single Prepper/Processor. Would the current proposal be of value to you? Do you...

Thanks @sbayer55 for putting that together. I have a similar concept, but it uses a `conditional_routing` Processor. Basically, this one Processor could route into other processors depending upon the condition....

Yes, you also have something similar for the processors. I like your syntax a bit more than mine - it's more readable.

If Data Prepper uses the Conditional Routing approach from #1007, this RFC should change to match it. I believe the following two changes are necessary: 1. Remove the `when` property...

@ryn9 , You expressed interest in if-else-elseif conditions within Data Prepper. I created a new proposal for conditional routing in #1007. It represents my current thinking on how to handle...

The discussion of the exact syntax Data Prepper will use has been moved into #1005.