-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Implement SLM Execute Retention API #4258
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've left a comment about the type names
@@ -36,6 +36,12 @@ public class ExecuteSnapshotLifecycleRequestParameters : RequestParameters<Execu | |||
public override HttpMethod DefaultHttpMethod => HttpMethod.PUT; | |||
} | |||
|
|||
///<summary>Request options for ExecuteRetention <para>https://www.elastic.co/guide/en/elasticsearch/reference/current/slm-api-execute-retention.html</para></summary> | |||
public class ExecuteRetentionRequestParameters : RequestParameters<ExecuteRetentionRequestParameters> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should the type name(s) be ExecuteSnapshotLifecycleRetention*
? The shortened method names are fine, because they reflect what is in the spec and are namespaced on SnapshotLifecycleManagement
, but with the types, these live in the root Nest
namespace, which feels like we ought to be more explicit to avoid naming collisions now and in future.
Ported to |
References: elastic/elasticsearch#47405