Deprecate discovery-azure and rename it to discovery-azure-classic #19144
Labels
discuss
:Distributed Coordination/Discovery-Plugins
Anything related to our integration plugins with EC2, GCP and Azure
Comments
|
Would definitely prefer a clean split so we can easily phase out |
dadoonet
added a commit
to dadoonet/elasticsearch
that referenced
this issue
Jun 30, 2016
As discussed at elastic/elasticsearch-cloud-azure#91 (comment), we know that the current `discovery-azure` plugin only works with Azure Classic VMs / Services (which is somehow Legacy now). The proposal here is to rename `discovery-azure` to `discovery-azure-classic` in case some users are using it. And deprecate it for 5.0. Closes elastic#19144.
clintongormley
added
:Distributed Coordination/Discovery-Plugins
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As discussed at elastic/elasticsearch-cloud-azure#91 (comment), we know that the current
discovery-azureplugin only works with Azure Classic VMs / Services (which is somehow Legacy now).The proposal here is to rename
discovery-azuretodiscovery-azure-classicin case some users are using it.And deprecate it for 5.0.
Note that the renaming already happened from 2.x to 5.0 because we split
cloud-azurein 2 plugins:discovery-azurerepository-azureWe can then work on a new
discovery-azure-armplugin if there is a need.Another option could be to provide classic and ARM in the same
discovery-azureplugin but this will mean that we will depend on multiple Azure SDK jars. Read https://github.com/Azure/azure-sdk-for-java/wiki/Azure-SDK-for-Java-FeaturesBut I don't think we should do it as it could potentially lead us to some JAR conflicts.
The text was updated successfully, but these errors were encountered: