Skip to content

Conversation

@andrershov
Copy link
Contributor

Follow-up of #45626.
Now we always output transport.publish_address with CNAME and log deprecation warning if es.transport.cname_in_publish_address property is specified.
This PR also adds a test which will fail once Elasticsearch version is changed to 9, to make sure we remove the property when doing reversioning.

Closes #39970

@andrershov andrershov added >non-issue :Distributed Coordination/Network Http and internode communication implementations v8.0.0 labels Aug 16, 2019
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-distributed

Copy link
Contributor

@original-brownbear original-brownbear left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@andrershov andrershov merged commit fab31ab into elastic:master Aug 22, 2019
DaveCTurner added a commit to DaveCTurner/elasticsearch that referenced this pull request Sep 18, 2024
This propery has been a deprecated no-op since elastic#45662 (8.0.0). This
commit removes it entirely in 9.0.0.
elasticsearchmachine pushed a commit that referenced this pull request Sep 18, 2024
This propery has been a deprecated no-op since #45662 (8.0.0). This
commit removes it entirely in 9.0.0.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

:Distributed Coordination/Network Http and internode communication implementations >non-issue v8.0.0-alpha1

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Transport's publish address should report its hostname

4 participants