Extract transport cluster settings/ilm execute logic #86941
Merged
Conversation
This file contains 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
Extract execute logic from the transport actions for cluster update settings and ILM put/delete to support future reuse for operator file based updates. Relates to elastic#86224
grcevski
added
>non-issue
:Core/Infra/Core
|
Pinging @elastic/es-core-infra (Team:Core/Infra) |
DaveCTurner
approved these changes
May 25, 2022
salvatore-campagna
pushed a commit
to salvatore-campagna/elasticsearch
that referenced
this pull request
May 26, 2022
Extract execute logic from the transport actions for cluster update settings and ILM put/delete to support future reuse for operator file based updates. Relates to elastic#86224
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Extract the execute logic from the transport actions for cluster update settings and ILM put/delete to support future reuse for operator file based updates.
This PR serves as a base for the follow-up work to actually implement file based settings. There's no particular reason why these two were chosen, other than diversity of operations: settings vs entities and elasticsearch core vs plugin.
Relates to #86224