Skip to content
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

Elasticsearch trust settings: Only add them to the update payload if there are changes. #859

Merged

Conversation

gigerdo
Copy link
Member

@gigerdo gigerdo commented Sep 20, 2024

The trust setting should only be added to the payload when they change. If they are left out of the payload, no changes to the trust will be made.

This is a partial fix/workaround for #842

Description

Related Issues

#842

Motivation and Context

How Has This Been Tested?

Types of Changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Refactoring (improves code quality but has no user-facing effect)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation

Readiness Checklist

  • My code follows the code style of this project
  • My change requires a change to the documentation
  • I have updated the documentation accordingly
  • I have added tests to cover my changes
  • All new and existing tests passed

…there are changes.

The trust setting should only be added to the payload when they change. If they are left out of the payload, no changes to the trust will be made.
@gigerdo gigerdo force-pushed the only-update-trust-if-there-are-changes branch from 4495f4f to 21c4864 Compare September 20, 2024 14:16
@gigerdo gigerdo marked this pull request as ready for review September 20, 2024 14:19
@gigerdo gigerdo requested a review from a team as a code owner September 20, 2024 14:19
@gigerdo gigerdo merged commit 713dcac into elastic:master Sep 23, 2024
3 checks passed
@gigerdo gigerdo deleted the only-update-trust-if-there-are-changes branch September 23, 2024 18:23
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