Skip to content

Conversation

@Mpdreamz
Copy link
Member

@Mpdreamz Mpdreamz commented Jan 9, 2019

No description provided.

Copy link
Contributor

@russcam russcam left a comment

Choose a reason for hiding this comment

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

LGTM. Left one small nitpick

public partial interface IElasticClient
{
/// <summary>
/// This API will decrypt and re-read the entire keystore, on every cluster node, but only the reloadable secure settings will
Copy link
Contributor

Choose a reason for hiding this comment

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

I think this would flow better starting with "Decrypts and re-reads the entire keystore..."

Copy link
Member Author

Choose a reason for hiding this comment

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

I took this from the elasticsearch docs, inclined to leave it as. Want to at some point have descriptions as part of the json spec.

Copy link
Contributor

Choose a reason for hiding this comment

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

I should have been more clear; I think the description is fine, but dislike that it starts with "This API...". This feels superfluous when reading XML docs

Copy link
Member Author

Choose a reason for hiding this comment

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

I addressed that comment on the ccr PR and not here. Bit random on my part but your point is absolutely.correct it's superuous :)

@Mpdreamz Mpdreamz merged commit 43f6ecb into 6.5 Jan 25, 2019
@Mpdreamz Mpdreamz deleted the v65/reload-secure-settings branch January 25, 2019 09:56
Mpdreamz added a commit that referenced this pull request Jan 28, 2019
Mpdreamz added a commit that referenced this pull request Mar 29, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants