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

There is a lot of activity in Data Prepper, and not all of it is ready for production. I'd like to be able to get these features out to users in an experimental form than try to hide or remove them, or use feature branches.

Describe the solution you'd like

Introduce a concept of "experimental" features. These are not production-ready. They may change between minor versions.

This will mostly be a feature of documentation. However, we can also have an annotation to mark a plugin as experimental.

@DataPrepperPlugin(name="experimental_source")
@Experimental
public class ExperimentalSource implements Source

Some initial candidates:

• S3 scan
• RSS source

Disabling experimental features

By default, experimental features can be disabled so that they do not run. We could enable them using data-prepper-config.yaml

The simplest is to allow enabling all experimental.

experimental:
  enable_all: true

This structure could be expanded to allow enabling specific plugins.

experimental:
  enable:
    source:
      - rss
      - neptune