Skip to content

move ILM client objects from protocol to client #33532

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

Merged
merged 1 commit into from
Sep 7, 2018

Conversation

talevy
Copy link
Contributor

@talevy talevy commented Sep 7, 2018

pretty straightforward migration (assuming this is correct)

@talevy talevy added the :Data Management/ILM+SLM Index and Snapshot lifecycle management label Sep 7, 2018
@talevy talevy requested a review from gwbrown September 7, 2018 19:44
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-infra

Copy link
Contributor

@gwbrown gwbrown left a comment

Choose a reason for hiding this comment

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

This works for resolving your immediate problem, although long-term we want to switch to having the Request objects implement Validatable rather than extend ActionRequest (or subclasses thereof). That said, this is a good first step and those hierarchy changes can be done later if you're in a hurry.

If you want to make those changes in this PR though, that would be great.

@talevy
Copy link
Contributor Author

talevy commented Sep 7, 2018

thanks @gwbrown. cleaning up the hierarchy can be done at a later time

@talevy talevy merged commit e0b99d7 into elastic:index-lifecycle Sep 7, 2018
@talevy talevy deleted the ilm-migrate-client branch September 7, 2018 22:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Data Management/ILM+SLM Index and Snapshot lifecycle management
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants