The elasticsearch destination plugin will work better with composer if it's separated out as it will have a direct dependency. We can also run a 1.x with elasticsearch 7, and 2.x with elasticsearch 8. This will unblock running 2.x with bugfixes with the appropriate elasticsearch library on larger sites.
Split out the code into a separate module.
You will need to `composer install drupal/data_pipelines_elasticsearch` if you're using it. The new module is compatible with current module so no settings should need to be changed.
Active
2.0
Code
Issue #3511755: Move elasticsearch destination plugin to a separate...
Automatically closed - issue fixed for 2 weeks with no activity.