Move ccr info/usage actions into ccr module #78137
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
The ccr info and usage actions provide information through the xpack usage nad info apis. The implemenation classes should be in each individual module, yet for ccr they exist in xpack core, splitting the ccr package. This commit moves the classes into the ccr module to fix the split package.
rjernst
added
>non-issue
:Distributed Indexing/CCR
elasticmachine
added
the
Team:Distributed (Obsolete)
|
Pinging @elastic/es-distributed (Team:Distributed) |
|
@elasticmachine update branch |
|
@elasticmachine run elasticsearch-ci/part-2 |
58 tasks
henningandersen
approved these changes
Sep 22, 2021
It should still work in 7.x, just needs a different change. I'll backport it manually. |
|
Oh good news, the backport isn't even needed. In 7.x the info/usage classes are not in the same location, and there is no split package. |
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.
The ccr info and usage actions provide information through the xpack
usage nad info apis. The implemenation classes should be in each
individual module, yet for ccr they exist in xpack core, splitting the
ccr package. This commit moves the classes into the ccr module to fix
the split package.