Adding deprecation info API check for client transport profile setting #76999
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
elasticmachine
added
the
Team:Data Management
Collaborator
|
Pinging @elastic/es-data-management (Team:Data Management) |
80 tasks
jbaiera
approved these changes
Sep 1, 2021
| ClusterState cs, | ||
| XPackLicenseState licenseState | ||
| ) { | ||
| final Setting.AffixSetting<String> TRANSPORT_TYPE_PROFILE_SETTING = |
masseyke
deleted the
feature/deprecation-info-transport-client-profiles-filter
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In 8.0, access to the transport client has been removed, so the transport.profiles.*.xpack.security.type
setting is gone. This commit adds a deprecation info API check for this property.
Relates #42404 #43236