New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HLRC XPack protocol clean up #34451
Comments
Pinging @elastic/es-core-infra |
I think it would be good to also clean up the existing actions we moved from, for instance, we tended to add some XContent methods to the existing request/response that are not needed, so lets try to also revert the history of the moved code in the x-pack directory to something that was before we started the migration. |
Drop protocol module Relates elastic#34451
Move parts related to XPack for packages Migration; Graph; Watcher from protocol to client Drop protocol module Relates #34451
Move parts related to XPack for packages Migration; Graph; Watcher from protocol to client Drop protocol module Relates elastic#34451, backport of elastic#34639 (cherry picked from commit 69fe9a1)
Move parts related to XPack for packages Migration; Graph; Watcher from protocol to client Drop protocol module Relates #34451
Relates elastic#34451 , backports elastic#34547 (cherry picked from commit 28bb1a3)
This can be closed as we will likely not modify them, and instead wait to do the work of generation of the code. |
Relates to XPack HLRC #29827
There are some requests/responses in xpack protocol, while most requests/responses are in client/rest-high-level (proper place)
Move ( + clean up ) HLRC located at xpack protocol to client/rest-high-level
Note: In most cases everything is there, except maybe some tests like RequestConvertersTests and unit tests.
Clean up assumes don't extend
AcknowledgedRequest
,readFrom(StreamInput in)
/writeTo(StreamOutput out)
The text was updated successfully, but these errors were encountered: